Unnecessary rebuilt of dependencies?
Unnecessary rebuilt of dependencies?
- Subject: Unnecessary rebuilt of dependencies?
- From: marc hoffman <email@hidden>
- Date: Thu, 31 Dec 2009 19:34:21 +0100
Hi,
i'm wondering if anyone has an idea on this:
i have two unrelated Xcode application projects. both projects use a couple of shared frameworks, which i reference in via their xcodeproj (and not via precompiled frameworks), because i do a lot of work on the frameworks themselves, while working on the main apps.
when i work on any individual project, the dependency checking works fine. if i make a change to framework X, and builds project A, it builds both X and A, if i make changes local to project A only, it only builds project A. the same happens in project B. so far so good.
however, every time i switch between project A and B, all the frameworks get rebuilt completely as well, ebven if nothing changed. example steps-
- build project A
- build A again => nothing much happens. as expected.
- build project B => full rebuild happens
- build B again => nothing happen
- build project A => full rebuild happens.
both app projects use the same settings (Debug, 10.6 base SDK, 32/64 intel-only universal, "build active only").
anyone have an idea how building project A would trigger the frameworks needing a rebuild for project B, and vice versa? if nothing changes in the framework project's xcodeproj, and their files don't change?
any ideas would be appreciated,
marc
ps: happy new year! ;) _______________________________________________
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