DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29461>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29461 Cygwin & path to build file Summary: Cygwin & path to build file Product: Ant Version: 1.6.1 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: Wrapper scripts AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I experienced difficulties trying to install the globus toolkit whose build system heavily relies on shell and perl scripts as well as on make and ant. I tried to perform the build under the cygwin environment. ant is several times called with the buildfile option, where the path contains an absolute path to the build file, for example ant -f $SOME_PATH/build.xml where $SOME_PATH could expand to '/cygdrive/c/some/path' or, if local windows drives are mounted '/c/some/path'. As I inspected the ant wrapper script, the home directories of Ant, Java and the user as well as the local classpath are converted. For the most applications, this will suffice. However, there are more possibilities to crash the build with an absolute cygwin-style path: * as mentioned the path to the buildfile (-f, -file, -buildfile) * -lib * -logfile, -l * -propertyfile * file paths in properties, for example -Dapp.home=/cygdrive/c/some/path Simply extending the wrapper script would work, but is this the rihgt approach? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
