Re: Xcode 2.0 upgrade glitch
Re: Xcode 2.0 upgrade glitch
- Subject: Re: Xcode 2.0 upgrade glitch
- From: Paul Russell <email@hidden>
- Date: Sun, 8 May 2005 22:08:54 +0100
On 8 May 2005, at 10:19, j o a r wrote:
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.
Thanks for the confirmation - that's pretty much as I feared - the only
way i can see this working in practice is if we make all developer
machines have two disks or partitions, one with OS X 10.3 and XCode
1.5, the other with OS X 10.4/XCode 2.0. I think we'll probably also
need to maintain two versions of every current Xcode project in
parallel for some time, which is going to be rather painful.
Paul
_______________________________________________
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