Re: Build location paths and build-product-relative paths
Re: Build location paths and build-product-relative paths
- Subject: Re: Build location paths and build-product-relative paths
- From: James Walker <email@hidden>
- Date: Tue, 26 Jun 2007 16:16:07 -0700
Chris Espinosa wrote:
On Jun 26, 2007, at 3:36 PM, James Walker wrote:
Chris Espinosa wrote:
On Jun 26, 2007, at 11:57 AM, James Walker wrote:
There are build settings for Build Locations, but the General tab of
the project's Info window also has "Place Build Products In" and
"Place Intermediate Build Files In" paths. How are these settings
supposed to interact? When the General settings disagreed with the
build settings, I was getting erratic behavior of
build-product-relative paths. They'd seem to work, but then after
the project was closed and reopened, they'd be broken. This is in
Xcode 2.4.1.
The settings in Xcode Preferences set Xcode-wide globals (stored in
Xcode's per-user preferences file) that are used as the base location
for all projects opened by that user.
Oh, I didn't know about the setting in Preferences...
Then that shouldn't enter into it...
Projects usually inherit this setting, but projects can override it,
either relatively or absolutely, on a project-by-project basis. If a
project has a specific SYMROOT and OBJROOT, that should apply to all
targets in that project
SYMROOT can also be set in the target settings. But what's still
confusing me is that there are apparently two different places to set
SYMROOT at the project level, one under the General tab and one under
the Build tab.
Those are the same, or at least /ought/ to be.
—but /note that it does not apply to other projects referred to by
that project as cross-project references. /(This is one reason we
keep saying that "corss-project references are not subprojects).
To diagnose brokenness, we'd need some specific case data.
<rdar://5296424>
Thanks. I see in your project you've defined SYMROOT to be
$(PROJECT_DIR)/../build-products in the Project build settings. It
/is/ odd that the General tab has "Default location" selected and the
path dimmed, while the custom location is clearly set in the Build tab.
That may be a bug.
When I follow the Steps to Reproduce (and interpolate that you mean to
choose "Relative to Build Product" when adding the file, as after all
that's what the bug is about)
Oops, right you are. I've updated the bug report to clarify that for
the record.
I get an odd relative path for the added file:
../../../../build-products/Debug/TestPath.txt
in red. If I make it "Relative to Project" and re-choose I get the
expected path, but you're right, it's not working with Relative to Build
Product.
We'll look into it, thanks for providing an isolated, detailed case.
You're welcome, thanks for the quick feedback.
--
James W. Walker, Innoventive Software LLC
<http://www.frameforge3d.com/>
_______________________________________________
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