Re: Is or Is Not XCode 3.1 supposed to replace 3.0
Re: Is or Is Not XCode 3.1 supposed to replace 3.0
- Subject: Re: Is or Is Not XCode 3.1 supposed to replace 3.0
- From: Bill Bumgarner <email@hidden>
- Date: Sun, 9 Mar 2008 13:09:15 -0700
On Mar 9, 2008, at 1:03 PM, William Squires wrote:
Just a simple yes/no question here, so hopefully doesn't violate
NDA on iPhone stuff. I installed the "new" XCode 3.1 (yes, from the
iPhone dev URL), and the readme ("About iPhone SDK.pdf") states that
one should create a new folder, or it'll overwrite XCode 3.0 if
installed in /Developer.
But none of the sample projects compile as it can't find the
headers (like, maybe, the paths are supposed to point to /
Developer/???) from within the precompiled header in the sample
projects. So is it, "yes, XCode 3.1 is separate from XCode 3.0" (in
which case the installer has a snafu), or "no, you're supposed to
use the package to UPDATE 3.0 -> 3.1"?
Xcode 3.1 is a beta release and, thus, is not qualified to produce
production binaries. So, if you have no need of shipping -- say -- a
new version of an existing application for Mac OS X, then replacing
Xcode 3.0 with 3.1 might likely be viable for you.
If, however, you need to continue to use Xcode 3.0 for Mac OS X
development / support, then I would suggest moving /Developer out of
the way and installing 3.1 into /Developer.
That is, move the 3.0 tools to -- say -- /Developer3.0/ and installing
Xcode 3.1 into the default location.
As with any beta, it is likely that there will random bugs and it
sounds like relocation of the developer tools suffers from a bug or two.
b.bum
_______________________________________________
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