From: Danny Smith <dannysmith@cl...> - 2004-03-26 08:13:52
----- Original Message -----
From: "Eddie Diener"
> How does it automatically find them ? Evidently it did for 3.2.3. What
> allows 3.3.1 to find them considering the location of the C++ header
> have changed ?
The code for determining default search path for system headers is
built into the gcc driver. For mingw32, the include search paths
include both the path constructed when gcc was built and a relocatable
search path that is constructed using 1) the directory in which the
driver is installed 2) the builtin version string and 3) the relative
path from the gcc driver to the compiler exec directory (eg, the
/my_mingw/bin/../lib/gcc-lib/mingw32/3.3.3 directory). Other default
search dirs may be added in the "specs" file in the exec dir.
To see what these builts in are just compile a dummy file with verbose
gcc -v -c nul.c
g++ -v -c nul.C
> It should be clearly documented and easily obtainable from
> somewhere. It is very difficulty to be convinced of the superiority of
> vaunted C++ compiler if the simplest information regarding it can not
> found. I am sorry to be piqued by this, but I have asked this same
> on the GCC/G++ listserver and I have gotten the same lack of a
> answer. Does no one actually know how this works ?
Probably not. As with all free software, it's a well hidden secret.