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 17:13:05 -0700
On May 22, 2011, at 4:38 PM, G S wrote:
> I couldn't figure out what Xcode was trying to do when autocreating schemes from our Xcode 3 project. I eventually decided that it confused "device" and "simulator" with "Debug" and "Release", but it turns out that's not right either.
>
> Why does Xcode add a bunch of simulator destinations to "device" schemes, and a device destination to "simulator" schemes? Look at this nonsense:
It is relatively unusual to have separate simulator & device targets to start with. The iOS SDK designates that the legal destinations for a target are any connected devices plus the simulator, hence why it adds the simulator as a destination in the pull down.
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.
--
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