ext Bryce Schober wrote: > FYI, my probably was actually my own time.h in one of my added include > paths. I see that the GCC documentation says that the -I option adds > include paths ahead of the system includes, but I always thought that > using the angle-bracket form of #include only search system include > paths, not user include paths. Apparently that's not true. Does anyone > have any clarification to offer?
Just that you're not the first one who is bitten by this :) Both (as you already pointed out) gcc and also MSVC search header files in include paths given on the command line. The difference is rather that #include <..> does not search in the 'local' directories. So you should - avoid using already existing file names for your header files - avoid excessive use of -I for a project with multiple folders. http://gcc.gnu.org/onlinedocs/gcc-4.4.2//cpp/Include-Syntax.html#Include-Syntax http://msdn.microsoft.com/de-de/library/36k2cdd4.aspx Kai -- Kai Koehne Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
