Hi,
I always have an impression that for the following semantics:
#include <something e.g. #include <stdio.h>
Compiler searches it from built-in header search path, on UNIX, it
could be /usr/include, /bin/include.
And for the following semantics:
#include "someting" e.g. #include "mine.h"
Compiler searches it according to the -I command option and the
built-in search path.
But I just encountered a problem, it is Visual C++ compiler, it
seems for #include <type, it also search for -I path. And it
automatically add "include" to the end of -I path, here is an example:
I have -I c:/repo in VC compiler path and in my C code, I have:
#include <auto_arraywhile the file actually locates at c:/repo/
include/auto_array, but VC compiler finds it.
Could you confirm 2 things:
1. Compiler searches builtin path and -I command option for both
"#include <>" and "#include "" " type include.
2. Compiler add "include" to the end of each search path named in -I
option.
Here is copy & paste from my compile command:
c:/msvsn2003/vc7/bin/cl.exe -W3 -Tp ../s/TestUtils.c -c -nologo -GR -
MDd -Ob2 -Zi -GX -DDEBUG -DNT -DNO_TCL_STUBS -FdlibTestUtils.pdb -
FplibTestUtils.pch -Ic:/repo -I../i
TestUtils.c
Thanks.