Re: Specifying build location
Re: Specifying build location
- Subject: Re: Specifying build location
- From: Michael Cashwell <email@hidden>
- Date: Thu, 23 Sep 2004 21:26:27 -0400
Unless I'm confused these two suggestions really aren't that different. If you look back at my script you'll see that it is an install build action done via xcodebuild as Chris said. I just had two additional needs that I couldn't figure out how to do without overriding the OBJ and SYM roots.
One was that build products and intermediates not stomp on each other. And the other was that I needed 2 flavors of Deployment builds, one that ended with the normal build products together but not in their installed hierarchies and one with the install hierarchy that also did the package maker and disk image post processing.
You can certainly adopt just the parts that make sense for your case. If you don't need multiple flavors of deploy builds and you don't care if the different styles' products and intermediates interfere with each other (ie: clean and full rebuild when switching is acceptable) then you probably don't need the the variable overrides. You could just use the Install Path of the Deployment style directly.
However, if you have a multi-project workflow (where one's products are inputs to another) and multiple developers then you may still want to force the intermediate and build products to be set by the project. It depends on how you've set things up.
As to the meaning of "install", I think of it as building FOR installation, not that it DOES the installation. It's simply an unfortunate false cognate that an install target in a classical make-based system does so. I just put that aside when dealing with Xcode and accept the difference in the use of the word.
HTH.
-Mike
On Sep 23, 2004, at 4:52 PM, Matt Gillette wrote:
Hi,
I now have more of a philosophical question. Should I take chris' advice and use xcodebuild install or should I instead redefine SYMROOT as Mike suggested? I'm a little confused by why it's called install - since I'm not installing (although you could argue about the definition of install). Is there any difference between the two methods (assume I set SYMROOT in my call to xcodebuild).
Thanks,
Matt
BTW I made a radar asking to make it clear that the build location in the project is per user.
rdar:// 3813385
On Sep 22, 2004, at 1:07 PM, Chris Hanson wrote:
On Sep 22, 2004, at 11:03 AM, Matt Gillette wrote:
Is there a way to specify a build location for an individual project? I want to set the build location for a deployment build for one project. This setting must be stored in the project, and not be based on user. It seems like the option in the project setting should be per project, not per user as it is.
I think your best bet is to learn the ins and outs of the xcodebuild command-line tool, and to set up a simple script that uses it to produce a release.
This way you're not mandating anything about how developers set up their systems (except perhaps - if you have multiple interacting/dependent projects - that they build all projects to some common directory of their choosing), and you have some very simple information to communicate to whoever does your builds.
Check out the xcodebuild(1) man page for more details. In particular, check out the "install" buildaction and the DSTROOT setting.
-- Chris
_______________________________________________
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