I've installed Xcode 3.1.2 (stand alone, no iPhone SDK) on Mac OS X v10.5.7 and I want to replace it with the new version of Xcode. Have I to uninstall Xcode 3.1.2 before to install Xcode 3.1.3?
Is better Just to upgrade the previous version of Xcode or make a new installation from scratch?
Thanks.
Luca.
From: email@hidden
Date: Wed, 17 Jun 2009 17:37:21 -0700
To: email@hidden
Subject: Xcode 3.1.3 Release Notes
Xcode 3.1.3 Release Notes
Xcode 3.1.3 is an update to the Xcode development environment. It works only on Mac OS X v10.5 Leopard and can be installed either alongside or replacing Xcode 3.1.2 or earlier.
Summary of changes from Xcode 3.1.2
Like Xcode 3.1.2, Xcode 3.1.3 has no significant new features over Xcode 3.1. It adds some minor enhancements, refines the iPhone development experience especially in the use of provisioning profiles and code signing, and fixes a small number of bugs.
General
-
Supported configurations
Xcode 3.1.3 runs on Mac OS X v10.5 Leopard on a Macintosh with either a PowerPC or an Intel processor. It does not install or run on earlier versions of Mac OS X. Xcode supports development for universal development for Mac OS X v10.4 Tiger and Mac OS X v10.5 using the Mac OS X SDKs. It also supports cross-development for the iPhone, iPod touch, and iPhone Simulator using the iPhone SDKs, but only on Macintosh computers with an Intel processor.
Warning: Xcode 3.1 3 works only with the iPhone SDK packages delivered with the iPhone 3.0 SDK. If you have installed previous releases of the iPhone SDK, you must upgrade to the current release of the iPhone SDK when upgrading to Xcode 3.1.3. You can still develop for iPhone OS 2.0 through 2.2.1 as well as 3.0 using the iPhone 3.0 SDK.
-
Xcode Installation
The directory on which the Xcode toolset is installed is known as <Xcode>, which by default is the /Developer directory. But you may install Xcode 3.1.3 on any volume in any location, and you can move or rename the <Xcode> directory after installation. The only restriction is that the directory names of its subdirectories must not be changed or moved within the Developer directory. The <Xcode> directory itself may be renamed and placed in any other directory or volume, including servers and external drives.
This flexibility allows you to have multiple versions of the Xcode toolset installed on the same computer but running independently. Xcode uses the SDKs, build tools, and auxiliary applications from the <Xcode> directory it is launched from whenever possible, rather than those from the root system.
Warning: If you have installed a previous version of the iPhone SDK, you must install iPhone SDK 3.0 in order to get a correct installation of Xcode 3.1.3. Do not install the Xcode 3.1.3 package separately.
-
Project File Format Compatibility
Xcode 3.1.3 reads and builds the targets of project files created in Xcode 2.1 through 3.1.2, and automatically upgrades project files created in Xcode 1.5 through 2.0.
Project files opened and edited with Xcode 3.1.3 are generally compatible with Xcode 3.1.2, 3.1.1, 3.1, 3.0, and 2.5; this means that project files you create or open with Xcode 3.1.3 can always be opened and built with Xcode 3.1.2, 3.1.1, 3.1, 3.0, and 2.5. There are no incompatibilities between Xcode 3.1.3 and 3.1, though bug fixes may make projects build correctly in 3.1.3 that will not build correctly in earlier versions.
If you use a particular feature that would cause your project to fail to build on an earlier version of Xcode, you see a Compatibility Notice in the bottom-right corner of your project window. Click Show Conflicts in the General pane of the Project Info window to investigate and resolve the compatibility issue.
Summary of New Features
-
You can now open multiple memory browser windows in the debugger at a time.
-
The Active SDK menu and pop-up menu, and the Active SDK section of the Overview pop-up menu in the toolbar now show “Base SDK” rather that “(Project Settings)” to denote when the active target builds with the SDK that’s set in its Base SDK build setting, rather than with an override you designate with the Overview pop-up menu.
-
The options for the active SDK setting in the user interface are now restricted to SDKs that are known to be compatible with the project’s Deployment Target. You cannot set an active SDK (override) to an SDK version that is older than the Deployment Target allows. Since the Deployment Target is in most cases driven by the Base SDK, this means you cannot set the active SDK to be earlier than the Base SDK.
-
Similarly, the options for active executable are now restricted to the capabilities of the Deployment Target and the current development environment. For example, if iPhone Simulator does not support a specific SDK, an option to launch that version is not shown.
-
A new build setting, XCODE_VERSION_MINOR, allows you to distinguish Xcode 3.1.x from earlier or later versions without regard to the update version. For Xcode 3.1.3, its value is 0310.
-
A new command-line tool, xcrun, allows the command line user or scripter to locate and execute tools in the build chain for specific platforms and SDKs. See the man page for xcrun(1) for details.
-
Xcode 3.1.3 contains an updated version of GCC 4.2 with several code generation bug fixes. See the GCC release notes for details.
-
An option in the Executables inspector allows you to wait for the executable to be launched or receive a push notification before attaching. This allows you to debug applications launched via a URL or push notification.
-
The New Project dialog has fewer and clearer choices for project templates; you now choose a basic template and use options to indicate variations of it.
Significant Bug Fixes from Xcode 3.1.2
- Xcode no longer changes the Default Keychain when code signing your project if another application has the login keychain open. 6229180
-
A bug where the Copy Strings phase would fail with non-UTF-16 strings files has been fixed. 6319655
-
It is easier to revert the Code Signing Identity to the default iPhone Developer and disassociate the project from installed provisioning profiles. 6415857
-
Syncing with Mobile Me now no longer causes Xcode to spin. 6449377
-
Edit All in Scope no longer crashes when typing certain composed Unicode characters. 6217303
-
A bug causing the first build to fail with “No architectures to compile for” has been fixed. 6465913
-
Changes to the Overview pop-up menu in the Project window toolbar are reflected in toolbars in other windows (and stick). 6484921
-
Disclosure triangles in the debugger’s Variables pane now stay in their set state, rather than reverting spontaneously. 4298505
-
An extremely common problem where compiler build settings would not be visible if the Active SDK pop-up menu is set differently than the Base SDK has been fixed. 6394765
-
Code signing no longer attempts to sign static library build products. 6326119
-
Xcode now clears its cache of code-sign identity certificates when the keychain changes. This avoids the reuse of stale identities. 6377212
-
Code-signing profiles are now more clearly grouped with their matching provisioning profiles in the Code Sign Identity build setting value pop-up menu. 6272147
-
Bringing up the Find window no longer switches spaces. 5308807
-
Breakpoints set during debugging are hit even if no breakpoints were set at launch. 6319852
-
The dialog used to add libraries and frameworks does not show frameworks that have no public headers. 6491540
-
The Attach to Running Process command for remote computers no longer fails if there is a process with the same PID on the host. 6642629
-
The debugger shows ARM and VFP registers correctly. 6611937, 6661939
View your Twitter and Flickr updates from one place – Learn more!
|