Re: "Run" runs the app in the wrong target
Re: "Run" runs the app in the wrong target
- Subject: Re: "Run" runs the app in the wrong target
- From: Andy Lee <email@hidden>
- Date: Wed, 27 Aug 2008 13:31:55 -0400
On Aug 27, 2008, at 1:11 PM, Ken Thomases wrote:
On Aug 27, 2008, at 11:35 AM, Andy Lee wrote:
I wanted Xcode to build two versions of the same app -- let's call
them AppOne and AppTwo -- that differ only by an #ifdef in a few
places in my code. So I duplicated the target for AppOne and
tweaked some settings in the duplicate target, which I renamed
AppTwo. (I also created an aggregate target that has AppOne and
AppTwo as dependencies, but I don't think that's relevant to my
question.)
This seems like the sort of thing more easily handled by creating a
new build configuration.
I did it this way because I want to release both versions of the app
separately, and I wanted to be able to build, run, and debug them
independently. But I'm not too conversant with the nuts and bolts of
Xcode's build machinery, so I might be missing a simpler way to do it.
If I select AppTwo as the active target and say Build, it gets
built as I would expect, with the name AppTwo.app. But when I say
Run, Xcode launches AppOne (or if AppOne hasn't been built, the Run
command is not available).
My question is: how do I tell Xcode to run AppTwo and not AppOne
when the AppTwo target is active?
Project > Set Active Executable
Thanks! It's funny how many menu items I never noticed before.
--Andy
_______________________________________________
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