|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
Here are some commonly-reported issues that are known with this release of Xcode.
• Spaces in project path items
Any build setting that contains a path (or includes another build setting that resolves to a path) must be enclosed in double quotes if the path is likely to contain a space character. Xcode will handle the quoted value correctly, but will fail if an unquoted value resolves to a path that includes a space.
• Xcode 2.2 bug fixes may make projects incompatible with Xcode 2.1
The Xcode 2.2 file format and build system are backwards compatible with Xcode 2.1, but this does not extend to new features in Xcode 2.2 or Xcode features that have problems in Xcode 2.1. If you exploit a new feature or bug fix in Xcode 2.2 in your project, it may not work on Xcode 2.1. This includes (but is not limited to):
Using .xcconfig files in project-level build settings.
Compiler features like symbol separation, Essential Symbols, and per-architecture build settings.
Using macros in Run Script build phase input and output paths.
Includes and comments in .xcconfig files.
Projects and targets based on .xcconfig files that are missing at project load time.
Use of “User Header Search Paths” (USER_HEADER_SEARCH_PATHS), “Rez Prefix Files” (REZ_PREFIX_FILE, GCC_VERSION_IDENTIFIER, or other new build settings introduced in Xcode 2.2.
Reliance on the updated 10.4u SDK included with Xcode 2.2.
• Accessing Subproject Build Products in a Copy Files build phase
If you are using the default per-configuration build folders, a project may not be able to refer to the build products of a subproject in its Copy Files build phase. We recommend you use a shared build folder for projects that require access to each others’ build products.
• Issues When Using SDKs
When defining the “SDK Path” (SDKROOT) build setting for a project or target, consider explicitly defining the “Mac OS X Deployment Target” (MACOSX_DEPLOYMENT_TARGET) build setting to an appropriate value (usually, to the earliest release of Mac OS X on which the software should run). This can avoid certain compile-time or run-time errors by ensuring that the Xcode will generate code and use libraries appropriate for the release of Mac OS X you are targeting. If you use different SDKs per-architecture (e.g., SDK_ROOT_ppc), use the corresponding per-architecture deployment target setting (e.g., MACOSX_DEPLOYMENT_TARGET_ppc).
• Preprocessing Info.plist adds whitespace that causes XML parse failure
Using the Preprocess Info.plist feature may produce an invalid XML file. Adding the -traditional flag to “Info.plist Other Preprocessor Flags” may help.
• Limitations When Importing CodeWarrior 10 projects
Xcode 2.2 doesn't recognize the new optional text based project format available in CodeWarrior Development Studio for Mac OS v10.
• Project Find, Debugger, or other views are partially obscured
Changing screen geometry (due to adding/removing an external monitor or waking from sleep) may cause parts of the Xcode user interface to redraw wrong. Resizing the windows corrects this. This problem occurs only on Mac OS X 10.4.2 and earlier
_______________________________________________ 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
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.