On 4 Apr 2007, at 17:44, Chris Espinosa wrote:
On Apr 4, 2007, at 9:21 AM, Jerry wrote: On 4 Apr 2007, at 16:11, Andy Lee wrote:
On Apr 4, 2007, at 3:34 AM, Jerry wrote: When I change a header file in my project, Xcode doesn't compile the files which include that header. I end up, many times each day, searching for all includes of the header and manually recompiling the affected files. In bad cases I have to do a clean build, which wastes over an hour. Does anyone have any ideas of how I can move my build system into the twentieth century?
What if you select it, remove it from the project (make sure Xcode doesn't delete the file -- just remove it from the project), and drag it back into the project?
Makes no difference.
Actually, while trying to recreate the problem, I realized that I've misled you in the description - I think the problem is with multiple targets. If I have:
Target A, contains foo.h and foo.cpp Target B depends on target A, contains bar.cpp which includes foo.h
then when I change foo.h and build, foo.cpp gets compiled but bar.cpp doesn't. It looks like building target A effectively untouches foo.h.
What kind of target is A? Library, framework, ...? Are A and B in the same project? What kind of reference does target B use to refer to foo.h in A? (Relative to Project, absolute, ...?)
When you "build," what do you build? A, B, or an umbrella target that builds both?
And what version of Xcode?
A is a Carbon application, B is a static library, and A depends on B and links with its product library. They're both in the same project, and when I build, I'm building A, which causes B to be built first. Every file and group in the project is set to be "Relative to enclosing group" except for the top-level group which points to the root of the source tree, and is "Relative to Project". The project has over 2000 files which is why it took me a bit of time to track down what's going on....
My Xcode is version 2.4 and I'm on a MacBook Pro running 10.4.9.
Jerry
|