From: Danny S. <dan...@cl...> - 2003-03-05 09:45:31
|
Hi All this may be OT for mingw-dvlprs. If that is general opinion, I'll move off-list, but I think the distinction of runtime headers and w32api headers may have relevance to "native" mingw too. This message http://sources.redhat.com/ml/cygwin/2003-03/msg00271.html wanted the include/w32api dir to have priority over all other C include dirs with -mwin32 switch. Is there value in that? Currently all mwin32 does is add the -D_WIN32 series of defines for cygwin. Here is the order I have now (with or without -mwin32): #include "..." search starts here: #include <...> search starts here: /usr/include/c++/3.4 /usr/include/c++/3.4/i686-pc-cygwin /usr/include/c++/3.4/backward /usr/lib/gcc-lib/i686-pc-cygwin/3.4/include /usr/i686-pc-cygwin/include /usr/include /usr/i686-pc-cygwin/include/w32api /usr/include/w32api End of search list. -mno-win32 removes the w32api includes /usr/include/c++/3.4 /usr/include/c++/3.4/i686-pc-cygwin /usr/include/c++/3.4/backward /usr/lib/gcc-lib/i686-pc-cygwin/3.4/include /usr/i686-pc-cygwin/include /usr/include End of search list. -mno-cygwin does this: /usr/include/c++/3.4 /usr/include/c++/3.4/i686-pc-mingw32 /usr/include/c++/3.4/backward /usr/lib/gcc-lib/i686-pc-cygwin/3.4/include /usr/i686-pc-mingw32/include /usr/include/mingw /usr/include/w32api End of search list. Note that, for -mno-cygwin there is _no_ /usr/i686-pc-mingw32/include/w32api I'll start experimenting with .pch now to see how it interact with all this, before submitting anything. In longer term, it may be of value for mingw to separate out the w32api headers too, to make it easier to manage precompiled headers. Danny |