Re: Is dependency info supposed to persist?
Re: Is dependency info supposed to persist?
- Subject: Re: Is dependency info supposed to persist?
- From: Joar Wingfors <email@hidden>
- Date: Mon, 31 May 2010 08:44:22 -0700
How are the generated source files generated? Using script targets? If so, have you specified both input and output files to the script?
This is not the expected behavior for an "all-native" setup, but for some project configurations Xcode might not have enough information to track dependencies, and for that reason has to default to the safer approach of always building.
j o a r
On 31 maj 2010, at 07.37, Rush Manbert wrote:
> I have noticed that if I close Xcode, then open it and open a project that depends on targets in other projects, those targets always seem to compile everything as if I had done a clean. This happens even if I had just built the subproject target before I closed/reopened Xcode.
>
> This has reached the point where it's a bit me waster for me. We have a lot of static library projects and a couple of them have source code that is generated for every entity in a fair-sized database model. One has 270 files and the other has 140. Building a totally unnecessary triple-architecture Release build takes a long time, even on an 8 core machine. Distributed builds are not the answer either. Our tests show that they are generally slower than building on a single machine and they are never faster.
>
> It seems as if some dependency information is being lost that could easily be persisted or recreated. Is there anything I can do to help this situation? I'm using Xcode 3.2.2.
>
> - Rush
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden