Re: scheme change not changing project?
Re: scheme change not changing project?
- Subject: Re: scheme change not changing project?
- From: Fritz Anderson <email@hidden>
- Date: Wed, 23 Apr 2014 12:36:54 -0500
On 23 Apr 2014, at 11:59 AM, Chuck Soper <email@hidden> wrote:
> For one of the targets in an Xcode 5.1.1 project, I changed the scheme so
> that the Build Configuration was set to Distribution-AppStore instead of
> Release. This fixed the issue I was having, but when I was ready to commit
> and push with git, it shows that there are no changes.
>
> I¹m not sure if this is a .gitignore issue or an Xcode issue. Does any one
> have insight on this?
Apple’s apparent intention in schemes is that each developer would have a personal set of conditions for builds (think of parameter lists with absolute paths). If you want to share/control a scheme, use Product > Scheme > Manage Schemes… (also available through a button in the Scheme editor), and check the scheme off as “Shared.”
That will move the scheme out of your user-preference directory (which I bet is in your .gitignore file) into the general-use directory. Not only will it be maintained in the repo, your whole team will share that scheme.
Which means you should consider giving the shared scheme a distinctive name, to avoid colliding with personal schemes.
— F
--
Xcode 5 Start to Finish: Any day now. Really.
_______________________________________________
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