Printable View
Help me decide on the includes order for a MinGW implementation. The following is the current order:
Is this order correct?Quote:
C:\MinGW\lib\gcc\mingw32\3.4.5\include\
C:\MinGW\include\c++\3.4.5\backward\
C:\MinGW\include\c++\3.4.5\mingw32\
C:\MinGW\include\c++\3.4.5\
C:\MinGW\include\
I'm particularly curious as to the first and second entries. What exactly are the includes therein for? I can't find any documentation on it anywhere.
The first contains the c++ standard library headers. The second contains the non-standard c++ headers that presumably everyone used before the standard came into effect. I assume the second is for backward compatibility, particularly given the directory name.
The 3.4.5. refers to the version, as I'm sure you're aware; I have 3.4.2 in there as well and once more I suspect this is for backward compatibility.
The main include directory contains the winapi stuff.
Since there's unlikely to be a conflict between winapi and the 'latest' manifestation of the standard library headers, which I assume you'd prefer using, the include paths look good to me.
I too have 3.4.2 there. I removed them from the includes list recently because I don't expect much thrid-party 3.4.2 specific code to make its way into my machine.
I have the stlport on top of it all, where I believe it should be, correct?
Also have you checked the readme file inside the first entry (C:\MinGW\lib\gcc\mingw32\3.4.5\include\)? I cannot make sense of it.
Oops - I was looking in the wrong place for the first one in your include path; that one looks to contain c99 headers. I hadn't noticed the 'readme' before (shame on me, but I tend to skim these things, too, unless there's a pressingly urgent reason to do otherwise) but, having skimmed it (inevitably) it doesn't seem to be much to worry about; presumably a search will turn up more information regarding the 'fixmeincludes process' and the exact nature of the non-critical 'collateral inconvenience' referred to.
If your application uses stlport then its path should be first in the include path as you're doing, otherwise omit or, at least shift it to after the mingw standard c++ header include path.
If you've not already subscribed to the mingw-users mailing list then I'd like to recommend that you do so as I think you would find it a useful source of information and dialogue.
Thanks a bunch Ken.