It may be good advice not to do it. However, there's the case of environment variables, or parameter files containing Windows-style paths used in build.xml, for example. It appears that those variables are not converted sometimes, resulting in failures.
One of my build files refers to such a property. I get the DOS file warning at the start of the script, and further down, an error states that C:/cygdrive/c/Users/... couldn't be found. I wonder how Cygwin would come to creating such a hybrid path. Did anyone else run into this? The same script worked perfectly fine before I upgraded to 1.7. -e On Thu, Jan 21, 2010 at 5:59 AM, Dave Korn <dave.korn.cyg...@googlemail.com> wrote: > On 21/01/2010 01:11, Batson, Chuck wrote: > >> That is, how to avoid the warning in a "clean" way without resorting to >> the 'nodosfilewarning' option? > >> Say, for example, you create a Windows batch file containing the line: >> >> touch C:\foo.txt > > Well, don't do that then. > > 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
