Re: Why does Xcode create nonsensical destinations in every scheme?
Re: Why does Xcode create nonsensical destinations in every scheme?
- Subject: Re: Why does Xcode create nonsensical destinations in every scheme?
- From: David Duncan <email@hidden>
- Date: Sun, 22 May 2011 19:30:14 -0700
On May 22, 2011, at 6:45 PM, G S wrote:
> >Is there a particular problem you are trying to solve by having a target for device and simulator? There is probably another way to solve the problem that you are solving with multiple targets.
>
> Hm, so you're saying that Xcode is creating these because there were already separate targets?
Indeed. By default automatic schemes create one scheme for each target.
> If I remember correctly, I created two targets so I could link in different pre-built versions of the Boost System lib, one for simulator and one for device. But I'm not doing that for OpenSSL (which I'm also using pre-built), so I guess it's not necessary.
If you end up needing to do this again in the future, you should be able to do conditional target linker flags. Thus you can create a rule that conditionally links Debug/Simulator, Debug/Device, Release/Simulator, Release/Device without needing a second target.
Also for some complex projects its just better to turn off the automatic scheme creation. Usually this is because you have target dependencies configured, so for example you might add targets to build Boost, and have the main project depend on the Boost target. At that point you probably never care to build the Boost target directly, so you can turn off automatic scheme creation and remove that scheme.
--
David Duncan
_______________________________________________
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