• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: scheme change not changing project?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: scheme change not changing project?


  • Subject: Re: scheme change not changing project?
  • From: Chuck Soper <email@hidden>
  • Date: Wed, 23 Apr 2014 15:01:54 -0700
  • Thread-topic: scheme change not changing project?

Thanks Quincey Morris and Fritz Anderson for answering this quickly.

When committing, I had to check the box next to the <schemeName>.xcscheme
file. This is within xcshareddata/xcschemes. I was expecting that file to
be checked for the commit. I don’t have xcshareddata in my .gitignore file.

One more question below…

On 4/23/14, 10:36 AM, "Fritz Anderson" <email@hidden> wrote:
>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

Is it common practice to create a set of schemes that are shared and named
accordingly? This project has 4 targets, so we may need to have 8 schemes
(4 personal and 4 shared). It does seem like if the schemes are not
clearly marked Shared that people may inadvertently change a scheme for
the group. Or, people may change a scheme and expect it to be shared with
the group like I did.

Chuck



 _______________________________________________
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


  • Follow-Ups:
    • Re: scheme change not changing project?
      • From: Quincey Morris <email@hidden>
References: 
 >scheme change not changing project? (From: Chuck Soper <email@hidden>)
 >Re: scheme change not changing project? (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Codesigning and gatekeeper
  • Next by Date: Re: Run iOS unit tests from instruments w/o Xcode
  • Previous by thread: Re: scheme change not changing project?
  • Next by thread: Re: scheme change not changing project?
  • Index(es):
    • Date
    • Thread