Re: associate an Executable with an Aggregate Target?
Re: associate an Executable with an Aggregate Target?
- Subject: Re: associate an Executable with an Aggregate Target?
- From: Rua Haszard Morris <email@hidden>
- Date: Tue, 29 May 2007 14:55:58 +1200
Thanks for clearing that up.
Is there a possible enhancement here? Should I file a bug?
Because for me, the aggregate target does have a build product, it's
the build product of one of its dependencies. It makes sense that
Xcode shouldn't be able to guess where it is, but it seems sad that
Xcode can't be informed of the association. Especially when the
concept of "Executable" is handled in the nice way it is...
I see now that the Executable is associated with the whole project,
so I'm not sure how what I want fits with Xcode.
The 2 targets are necessarily part of the same project - they share
all the source files, with some conditional compilation, so having a
separate project would be impractical. Though moving all the code to
a static lib could work.... </digression>
On 29/05/2007, at 2:34 PM, Chris Hanson wrote:
On May 28, 2007, at 7:03 PM, Rua Haszard Morris wrote:
The problem is that the active executable is not chosen
appropriately when switching between the aggregate targets.
Is there a way to tell Xcode which executable goes with which target?
No. It happens for the targets that generate the executables
because the item in the project's Executables group was actually
created by that target to represent its build product and has a
strong association with it. There's no way to create that kind of
association manually for an aggregate target because it doesn't
have a build product.
-- 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