Re: dependent target "Copy files" build phase fails
Re: dependent target "Copy files" build phase fails
- Subject: Re: dependent target "Copy files" build phase fails
- From: Heath Raftery <email@hidden>
- Date: Wed, 28 Apr 2004 09:59:29 +1000
Hi Tommy,
On 27/04/2004, at 7:12 AM, Tommy Knowlton wrote:
I'd like to make an XCode project that depends on a target of an
external XCode project, such that the dependent target includes a
"copy files" build phase that copies the product of the precedent
target to the Executables folder of the dependent target's bundle.
If I understand you correctly, I've done something somewhat similar,
but perhaps with a significant difference - my tool, which I want to
include in my app's bundle, is just another target in my main project.
That is, I have the source for both targets in the one project and have
two seperate targets. One target depends on the other (so building the
app builds the tool first) and has a copy files phase which puts the
tool in the executable directory of the app's bundle. Works well.
Command-B build and watch the "copy files" build phase fail.
Does it give an error?
Now, maybe I could make this succeed if my Preferences were to send
build results to a separate location, but I don't think my whole dev
team should have to do that for this to work. By allowing the
precedent target to be dropped at the build phase, it ought to be
implied that the build phase knows how to locate the build products of
the precedent target.
Because I have both targets in the one project, I'm able to use the
tool's "product" icon to represent the build product. This is what I
use in the app's copy files phase.
Should I file an enhancement request? I'm obviously treading outside
the bounds of what's been well-tested, but I think this use case
should work. Else the UI should prevent me setting up the dependent
target in this way.
Yeah, that probably sounds fair to me.
Searching the xcode-users archive
(http://search.lists.apple.com/xcode-users?
q=dependent+target+"build+phase"+"copy+files") did not produce
any relevant results. Am I the only person that thinks this should
work?
Well... it is a fair stretch. I personally would not expect two xcode
projects to communicate well, but given that the GUI gave positive
feedback when you added one to the other, I'd start to think different.
Heath
_______________________________________________
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.