|
From: Earnie B. <ear...@ya...> - 2002-03-12 12:22:37
|
Earnie Boyd wrote: > > Richard Frith-Macdonald wrote: > > > > On Friday, March 8, 2002, at 06:31 PM, Earnie Boyd wrote: > > > > > Richard Frith-Macdonald wrote: > > >> > > >> This is probably a FAQ (though I can't seem to find an answer > > >> anywhere) ... > > >> > > >> What are the rules for path handling in mingw and msys? > > >> > > > > > > Discussed in the literature in the msys\1.0\doc directory. > > > > Thanks ... that helped somewhat ... though it would be good to know > > exactly > > what circumstances path translation is performed in when running mingw > > tools > > It seems that any argument in the format of an msys path is converted > > to a windows path, but arguments like a '-I/usr/include' are not. > > > > Works for me. Note, you must use the MSYS shell and not the > COMMAND.COM/CMD.EXE shell for -I/usr/include to be translated as GCC and > friends aren't a part of MSYS but are a native version using MSVCRT.DLL. > Also, let me add that command line path translation isn't done at all for programs residing in /bin or /usr/bin. Those directories are reserved for msys-1.0.dll dependant binaries. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |