On Apr 5, 2007, at 1:14 AM, Jerry wrote: I've been investigating this a bit more and I now think the multiple targets thing is a red herring. Making my static library target the active target. I modified a header file, foo.h (not its real name), and built the target. Xcode built foo.cpp, but missed 38 other files which directly #include foo.h. I think I might be homing on on something here because foo.cpp is in the same folder as foo.h, but the other files aren't. foo.cpp has #include "foo.h", but the others have #include "Foo/foo.h" and the header file search path is set up to include the folder containing "Foo". The search paths are inherited from the project settings - not per-target settings.
Before anyone asks: there are no spaces or weird characters in any filenames or the path to the project.
This is very helpful, and worth filing a bug report on at this point. One more stab in the dark: is the project on a case-insensitive file system (HFS) and the enclosing folder's actual name is "foo" rather than "Foo"?
In such a case the case insensitivity of the file system would allow gcc to find the included header, but the case sensitivity of the dependency mechanism would fail.
Chris |
