Re: XCode's "Relative to Build Product" path type
Re: XCode's "Relative to Build Product" path type
- Subject: Re: XCode's "Relative to Build Product" path type
- From: Mason Mark <email@hidden>
- Date: Fri, 11 Nov 2005 00:08:14 +0900
On Nov 9, 2005, at 1:58 AM, Martin-Gilles Lavoie wrote:
Ugh...
I'm having a bit of a mud-wrestling experience with XCode's Path
Type options for included bundles/frameworks/other output files
from other projects.
All my projects have a Release and Debug build configurations. One
project ("A") makes use of cross-project reference to build other
(sub-) projects ("B", "C", "D"…) that build a number of bundles,
frameworks and other output files.
Once the "A" project builds, either the Release or Debug, the
corresponding build configuration in "B", "C" and "D" build their
corresponding build configuration. So far, so good.
In the project, I've included the output of B, C and D into various
product subdirectories: Frameworks, PlugIns and Resources. I've set
these path types of these files to "Relative to Build Products". In
theory, this is supposed to pick up B's output from either the /
build/Debug/ or build/Release/ output directory.
Yet, when I go a Get Info to re-examine the full path of the given
included file, from either the Debug or Release build configuration
of the "A" project, it always lists the same full path pointing to
the "Release" directory.
XCode doesn't seem to understand that I want A's Debug build to
include the B, C and D Debug output, ditto for A's Release build.
The documentation on this is ratter skimpy so I was wondering if I
was missing a crucial step, or perhaps my project is hosed somehow.
(As much as I hate to admit it, this was way simpler in CodeWarrior.)
For reference, I'm using XCode 2.2 preview 4.
Hi.
I ran into the exact same issue. The GUI implies that it will create
a path relative to the build location, but it actually makes a
relative path something like this:
../../../SomeFolder/MyBuild/Release/Foo.app
...which ends up always pointing to the Release build.
I have a Note To Self scribbled on my desk blotter to figure out the
precise details so I can file the Xcode guys a meaningful bug, but in
the meantime I solved my problem by opening the .xcodeproj package,
looking at the contained .pbxproj file in a text editor, searching
for the path that was screwed up, and manually deleting the
"../../.." junk and just leaving it as "Foo.app".
I am fairly certain this is a bug, that how you expect it to work is
the expected behavior, and that will be fixed, but that was my
interim solution.
Cheers,
--
Mason Mark
Five Speed Software, Inc.
_______________________________________________
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