Re: Xcode Project References
Re: Xcode Project References
- Subject: Re: Xcode Project References
- From: j o a r <email@hidden>
- Date: Thu, 10 Jun 2004 15:39:38 +0200
On 2004-06-10, at 14.50, joshua portway wrote:
> One thing that we found VERY important is that all of your projects
> need to be set to build to the same location (a "source tree" is the
> obvious way to do it). If they aren't all built to the same place you
> get all sort of rubbish with paths - especially, eg. when working with
> frameworks.
Yes, and that was one of my main questions to Apple. Is this really a
reasonable limitation? In my opinion it is a major problem with the
current implementation of project references. How is this supposed to
work in an environment where you maintain multiple branches of a
product (== everywhere)?
You place the burden on every developer in the organization to remember
to update the build products directory not only for the main project in
every branch, but also for every referenced project.
I have a project with 27 referenced projects (Had I known about this
limitation I would not have set it up in that way...). Imagine updating
the build products directory for these 1+27 projects every time you
branch...
Using project references in their current implementation, you also
loose the ability to do a quick clean test compilation like this:
xcodebuild SYMROOT="${PWD}/build/products"
OBJROOT="${PWD}/build/intermediates"
...as the referenced projects wouldn't pick up the provided build
directory.
j o a r
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.