Re: Xcode 2.0 upgrade glitch
Re: Xcode 2.0 upgrade glitch
- Subject: Re: Xcode 2.0 upgrade glitch
- From: j o a r <email@hidden>
- Date: Sun, 8 May 2005 11:19:36 +0200
On 8 maj 2005, at 10.36, Paul Russell wrote:
You're scaring me now.
I'm wondering how we manage the migration of a group of developers
working on multiple projects from Panther/Xcode 1.5 to Tiger/Xcode
2.0 ?
We have a large team of developers using Xcode, and we usually solve
this unfortunate problem by setting a date where all have to change
to the new version of Mac OS X + new version of Xcode.
You can upgrade to the new OS+Xcode platform ahead of your fellow
developers, as long as you don't check in your project file
modifications to CVS.
Do Xcode project files get irreversibly changed when you move from
1.5 to 2.0, or can you open a 1.5 project in 2.0, make changes and
then open it again later in 1.5 ?
When I've asked about this in the past, Apple has responded that it's
not supported to share projects with older versions of Xcode.
While they say that "the project file format has not changed", that
doesn't mean that they haven't added new keys+values to the newer
version of Xcode - and what an older version of Xcode will do with
these keys is probably undefined.
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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