On 22/01/2010 17:23, Eric Vautier wrote:
> FYI, the "faulty but perfectly logical" path in one of the two
> failures (I'll try to trace the other one as well) was arrived at
> from:
>
>
> 0. Invocation from sh build.sh (mid-script):
>
> ant clean get-common debug
>
> 1. Output of build script:
>
> AndroidApp
> BUILD FAILED
> C:\dev\prj\app4\AndroidApp\build.xml:343: Warning: Could not find file
> C:\cygdrive\c\dev\prj\app4\Common\target\Common.jar to copy.
>
> 2. Build target (lines 342-344):
>
> <target name="get-common">
> <copy file="${common-jar}" todir="libs" />
> </target>
>
> 3. Properties:
>
> <property name="common" location="${env.APP4_COMMON_ROOT}" />
> <property name="common-jar" value="${common}/target/Common.jar" />
>
> 4. Environment variable:
>
> APP4_COMMON_ROOT = C:\dev\prj\app4\Common
>
>
> Typing "ant clean get-common debug" works fine from the command line.
So, you are lumbered with some massive mish-mash of complex build scripts,
ANT, java, mixture of cygwin and native executables and god knows what else,
and somewhere down in the middle of it something's invoking what it probably
expects to be a win32 program and getting the cygwin version, or vice-versa.
Ouch. You're going to have to figure out what's going on way down in the
internals and try and extract a simple testcase.
cheers,
DaveK
--
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
