On Feb 4, 2009, at 1:06 PM, Daniel Dunbar wrote: > I don't think this is correct; I believe the -include searches > relative to the current working directory, not the main file. > -- > ddun...@milton:tmp$ mkdir x > ddun...@milton:tmp$ touch x/a.h > ddun...@milton:tmp$ mkdir y > ddun...@milton:tmp$ touch y/a.c > ddun...@milton:tmp$ gcc -fsyntax-only -include x/a.h y/a.c > ddun...@milton:tmp$ clang -fsyntax-only -include x/a.h y/a.c > <predefines>:90:10: error: 'x/a.h' file not found > #include "x/a.h" > ^ > 1 diagnostic generated. > -- > > Would it be terrible to give the predefines buffer a file entry, with > the path being the current working directory? This would also allow > things in the predefines buffer to have a valid source location...
Is this something that is needed in practice for something important? -Chris _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
