This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

mingw32-gcc and posix paths


I'm in the process of going from gcc3 to gcc4. For one project I need to
build both cygwin and win32 executables so "-mno-cygwin" to "mingw32-gcc"
was an initial hurdle.

However that is now sorted out, but one thing puzzles me. If the mingw32 is
a cygwin cross-compiler why does it not accept paths in the host format
(meaning cygwin, posix)? To me this seems very natural. Maybe  I'm biased,
but I see no other tools do that, expecting the command line to have the
format of the *target*.

mingw32-gcc also produces .d files in its native format by the way.




--
View this message in context: http://cygwin.1069669.n5.nabble.com/mingw32-gcc-and-posix-paths-tp92376.html
Sent from the Cygwin list mailing list archive at Nabble.com.

--
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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]