Shared builds folder vs. trunk and branch builds: any better solutions?
Shared builds folder vs. trunk and branch builds: any better solutions?
- Subject: Shared builds folder vs. trunk and branch builds: any better solutions?
- From: Jim Correia <email@hidden>
- Date: Sun, 10 Dec 2006 21:10:20 -0500
I have a fairly complex project in which many components are build by
sub-projects. So that all the sub-components can be located and
copied into the application package, I'm using a shared builds
folder. I've set this via the Xcode preference (so that I don't have
to explicitly set the build folder location for N sub-projects, where
N is a large number :-)).
This system works well when I'm only working on trunk builds. If I
start working on the release branch (or worse, trunk, the release
branch, and a feature/sandbox branch) things fall down. When I jump
from trunk to the branch, I have to remember to clean then build.
Is there currently any better solution than to manually clean when I
start working on a different branch?
Thanks,
Jim
_______________________________________________
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