X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4B5A1E48.6060803@etr-usa.com>
References: <81D39E818991E549B1F66EB6A7D18422BE8626 AT AVSMOEXCL02 DOT activision DOT com> 	 <4B57DF25 DOT 4040605 AT gmail DOT com> 	 <7f95d3561001220517k4fd93c6btdda02fd06596e97f AT mail DOT gmail DOT com> 	 <20100122154551 DOT GB4020 AT ednor DOT casa DOT cgf DOT cx> 	 <7f95d3561001220823md77as48d8128d396c8370 AT mail DOT gmail DOT com> 	 <4B59D9FC DOT 3070307 AT gmail DOT com> 	 <7f95d3561001220923i60a15fe6u71c36b0baeda3ebe AT mail DOT gmail DOT com> 	 <4B5A1E48 DOT 6060803 AT etr-usa DOT com>
Date: Sat, 23 Jan 2010 01:09:00 +0100
Message-ID: <7f95d3561001221609s1dd33bf6l71426d99eb13c135@mail.gmail.com>
Subject: Re: Design issue with new MS-DOS style path warning?
From: Eric Vautier <eric.vautier+cygwin AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Just to clear things up, none of the paths are hard-coded.
They are all obtained from environment variables or paths relative to
project root.
Only in the output from ant do they "look" absolute (the build has to
figure out an absolute path sooner or later...).

Again, the build script works perfectly fine, as long as it's not
called from within a shell script. "ant clean get-common debug" works
fine from the command line, but the same line fails with the error
mentioned when run from INSIDE a shell script.

And it's starting to look like an old Ant/Cygwin interaction issue,
slightly off-topic with regards to the original discussion.

http://www.eyt.ca/blog/item/136/ (dated)
http://ant.apache.org/manual/platform.html (mid-page: Cygwin is trouble!)

Seems this issue crops up again every now and then when cygwin or ant
comes out with an update.
-e

On Fri, Jan 22, 2010 at 10:53 PM, Warren Young <warren AT etr-usa DOT com> wrote:
> On 1/22/2010 10:23 AM, Eric Vautier wrote:
>>
>> =A0 =A0 =A0 =A0AndroidApp
>> =A0 =A0 =A0 =A0BUILD FAILED
>> =A0 =A0 =A0 =A0C:\dev\prj\app4\AndroidApp\build.xml:343: Warning: Could =
not find
>> file
>> =A0 =A0 =A0 =A0 C:\cygdrive\c\dev\prj\app4\Common\target\Common.jar to c=
opy.
>
> My first thought when I see things like this isn't "oh, bad idea, DOS sty=
le
> paths in Cygwin". =A0I think "oh, bad idea, absolute paths hard-coded int=
o a
> build system". =A0That makes it hard to build on any other system, becaus=
e it
> ranges from difficult to impossible to demand that everyone install outsi=
de
> dependencies in the same locations.
>
> There must be a tool you can use to generate the Ant files from something
> higher-level, which discovers the correct paths to use. =A0That tool could
> also abstract away the difference in path styles. =A0Something like Autom=
ake,
> Bakefile or CMake, but which knows how to create Ant files.
>
> That's where I'd put my effort, anyway.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple