You've *got* to be kidding. Arg. OK, I've changed all the project
so far to build to a common folder. Now to remember to do that for
all the remaining projects I still have to convert.
You can set this globally in the Building pane of the Xcode
Preferences, you don't need to do it per-project.
Unless you maintain multiple versions of your application
concurrently, in which case you would have to use per-project build
folders - right?
I've tried to convert our large project suite to use project
references several times - last time was this summer using Xcode 2.1.
I've always failed for one reason or another. With the early versions
of Xcode it was because of the bugs ( ;-) ), but recently I think
that it was only because project references in Xcode are not designed
to do what I want:
* Must work with multiple branches of a project
* Must allow individual developers on the team to easily set their
own build location
-> Means that you should have to set this only once - for the parent
project
-> Also means that this pref would have to be persisted in per-user
settings
We're using script targets -> xcodebuild as a workaround. It's not
pretty, but it does the job.
Radar: 4152093.
j o a r
Ps. I'm using project references in my hobby projects at home. When
it does work, it's really convenient!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
This email sent to email@hidden
