Re: Specifying Where The Build Product Should Be Placed
Re: Specifying Where The Build Product Should Be Placed
- Subject: Re: Specifying Where The Build Product Should Be Placed
- From: Scott Tooker <email@hidden>
- Date: Wed, 21 Sep 2005 15:02:05 -0700
On Sep 21, 2005, at 1:41 PM, Howard Rodstein wrote:
My application must reside in a specific place in a specific
folder. Thus I am trying to control where Xcode writes the build
product. To figure this out I am using a brand new Carbon
Application project created from File->New Project.
The Xcode 2.1 manual says:
You can override the build location used for an individual project
in the
General pane of the project inspector. To override the default
location
for a project¹s build products, use the options under "Place Build
Products In."
However, there is no "Place Build Products In" setting in the
project inspector for a project.
I read on this list:
Set "Deployment Location" to the path you want the product
installed in
and check the "Deployment Postprocessing" checkbox.
However, there is no place to enter a path under "Deployment
Location". It is just a checkbox. Also this setting gets into the
"install-build" area which the documentation says is done only from
the command line using xcodebuild, not from Xcode itself, so it
does not seem like the right approach for me.
If I set the Development Build Products Path setting to point to my
desired folder, it does write my application there except that it
is inside a folder named debug, not directly in my desired folder.
I'd be grateful if someone could explain how to control where my
application is written by Xcode.
Okay there are two things going on;
1) When doing development you can control the build results folder
being used via the Development Build Products Path setting. However,
by default we append the configuration name to this path to separate
different configurations. You can override this behavior by setting
CONFIGURATION_BUILD_DIR to $(SYMROOT) at the target or project level.
In the next release of Xcode, there will be better UI and
documentation about this.
2) You can perfom "deployment" or "install" builds of your
application where Xcode places the results in a sparse root that can
then be used to create a package if desired, or in simpler cases you
can just pull out the application. In this case you need to set
"Installation Path" in addition to checking "Deployment Location".
Checking "Deployment Postprocessing" is also a good idea. The
expectation is that you will only do installs or deployment builds
when building up a fully optimized version of your application.
Scott
Howard Rodstein
WaveMetrics
_______________________________________________
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
_______________________________________________
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