Retired Document
Important: This document may not represent best practices for current development. Links to downloads and other resources may no longer be valid.
An updated version of Build Settings Reference is now available in Xcode Help. To access it:
1. In Xcode, choose Help > Xcode Help, or open the Xcode Help website.
2. Search for “build settings.”
Introduction
Xcode uses build settings to specify aspects of the build process followed to generate a product. A build setting is a variable that determines how build tasks are performed.
You can customize most of the build settings listed in this document using the target and product editors in the Xcode application, configuration files, and xcodebuild
invocations. However, there are build settings that can be customized only through indirect means and build settings that are not customizable. Build settings that are not customizable do not have a “Default value” entry in their reference.
In addition, Xcode lets you assign conditional values to build settings. The conditions include build factors such as the architecture you’re targeting and the SDK you’re using. Build settings with conditional values are known as conditional build settings.
This document is intended for developers who need to get a deep understanding of how the Xcode build system works.
To fully understand how a target’s build settings affect a build and how they relate to one another, this document uses the following terms to describe each build setting and the build settings that relate to it.
- Alias
Additional name used to identify a build setting.
- bundle file path or bundle directory path
String that represents a location inside a bundled product. See Bundle Programming Guide for information on product bundles.
- C-based language
C, C++, Objective-C, and Objective-C++.
- C++–based language
C++, and Objective-C++.
- Companion
Build settings that are used in conjunction with the referring build setting to accomplish its action. If you customize the referring build setting, you should review the specifications of its companion build settings.
- Default value
The buildtime value of a build setting when there’s no corresponding setting specification for the target.
- Effector
Build setting whose value is used to compute the default value of the referring build setting.
- Effect
Build setting whose default value is computed using the value of the referring build setting.
- file path or directory path
String that represents a fully qualified filesystem path. When a path contains spaces, the path must be surrounded by single quotation marks (
'
) or double quotation marks ("
), or the spaces must be escaped with a backslash (\
).- filename
String that may contain numbers, letters, dashes (
-
), periods (.
) or underscores (_
).- identifier
String that may contain digits, letters, dashes (
-
), plus signs (+
), and underscores (_
).- installed product
A product configured for distribution to its users.
- installed product directory
Directory that represents the root directory (
/
) on a user’s computer.- number
String that may contain only digits.
- numeric identifier
String that may contain numbers and periods.
- option specification
String that may contain the characters an identifier may contain as well as spaces. When an option specification contains spaces, it must be surrounded by single quotation marks (
'
) or double quotation marks ("
).- Prerequisite
Expression that must be true for the referring build setting to take effect.
- Prerequisite for
The referring build setting’s value allows or suppresses the behavior specified by the referred build setting.
- project file path or project directory path
String that represents a location inside a project directory.
- Related to
Build setting with a conceptual relationship with the referring build setting except for prerequisites, companions, effects, and effectors.
- uniform type identifier (UTI)
String that specifies a type. This string uses the reverse-DNS (Domain Name System) to uniquely identify an item in a way that other systems can recognize. See Uniform Type Identifiers Overview for details on uniform type identifiers.
- Value
Value of a build setting at build time. This is not necessarily the build setting specification. See Build Settings for details.
This document assumes that all the Xcode SDKs are installed on your computer.
If you develop products using C++, you may need to customize these build settings in your targets:
GCC_WARN_EFFECTIVE_CPLUSPLUS_VIOLATIONS (Effective C++ Violation)
GCC_WARN_HIDDEN_VIRTUAL_FUNCTIONS (Hidden Virtual Functions)
STANDARD_C_PLUS_PLUS_LIBRARY_TYPE (C++ Standard Library Type)
Use these build settings to customize your debugging experience:
The following sections describe build settings you can use to customize a build or to inquire about a the configuration of a build at build time.
Copyright © 2016 Apple Inc. All Rights Reserved. Terms of Use | Privacy Policy | Updated: 2016-09-29