A string identifying the build system action being performed.
The locations of any sparse SDKs that should be layered on top of the one specified by Base SDK (SDKROOT). If more than one SDK is listed, the first one has highest precedence. Every SDK specified in this setting should be a "sparse" SDK, for example, not an SDK for an entire macOS release.
The group name or gid for the files listed under the Alternate Permissions Files (ALTERNATE_PERMISSIONS_FILES) setting.
Permissions used for the files listed under the Alternate Permissions Files (ALTERNATE_PERMISSIONS_FILES) setting.
The owner name or uid for the files listed under the Alternate Permissions Files (ALTERNATE_PERMISSIONS_FILES) setting.
List of files to which the alternate owner, group and permissions are applied.
If enabled, both #include <header.h>-style and #include "header.h"-style directives search the paths in User Header Search Paths (USER_HEADER_SEARCH_PATHS) before Header Search Paths (HEADER_SEARCH_PATHS). As a consequence, user headers, such as your own String.h header, have precedence over system headers when using #include <header.h>. This is done using the -iquote flag for the paths provided in User Header Search Paths. If disabled and your compiler fully supports separate user paths, user headers are only accessible with #include "header.h"-style preprocessor directives.
For backwards compatibility reasons, this setting is enabled by default. Disabling it is strongly recommended.
When enabled, this causes the compiler and linker to disallow use of APIs that are not available to app extensions and to disallow linking to frameworks that have not been built with this setting enabled.
Files copied with a Copy Files build phase are unchanged by default. Setting this to TRUE causes property list files (.plist) and Strings files to be converted as specified by Property List Output Encoding (PLIST_FILE_OUTPUT_FORMAT) and Strings File Output Encoding (STRINGS_FILE_OUTPUT_ENCODING).
A list of the architectures for which the product will be built. This is usually set to a predefined build setting provided by the platform. If more than one architecture is specified, a universal binary will be produced.
Name of the asset catalog app icon set whose contents will be merged into the Info.plist.
The name of a watch complication to use from the asset catalog.
Name of an asset catalog launch image set whose contents will be merged into the Info.plist.
Leaderboards in the asset catalog may optionally specify a Game Center identifier. If they do not, their name will be prefixed by this value to form an automatically generated identifier.
Leaderboard sets in the asset catalog may optionally specify a Game Center identifier. If they do not, their name will be prefixed by this value to form an automatically generated identifier.
With no value, the compiler uses the default optimization. You can also specify time to optimize for speed of access or space to optimize for a smaller compiled asset catalogs.
Sticker Packs in the asset catalog may optionally specify an identifier. If they do not, their name will be prefixed by this value to form an automatically generated identifier.
Show notices encountered during the compilation of asset catalogs.
Pass additional flags through to the asset catalog compiler.
Show warnings encountered during the compilation of asset catalogs.
If set to anything other than the empty string, every URL in the AssetPackManifest.plist file will consist of this string with the name of the asset pack appended. If not set, the URLs in the AssetPackManifest.plist will be formed as appropriate for the build location of the asset packs. The prefix string is not escaped or quoted in any way, so any necessary escaping must be part of the URL string. This setting affects only URLs in the AssetPackManifest.plist file — it does not affect where asset packs are built in the local file system.
A list of components being built during this action.
A list of the build variants of the linked binary that will be produced. By default, only the normal variant is produced. Other common values include debug and profile.
Identifies the directory under which all the product’s files can be found. This directory contains either product files or symbolic links to them. Run Script build phases can use the value of this build setting as a convenient way to refer to the product files built by one or more targets even when these files are scattered throughout a directory hierarchy (for example, when DEPLOYMENT_LOCATION is set to YES.
Specifies the executable that will load the bundle output file being linked. Undefined symbols from the bundle are checked against the specified executable as if it is one of the dynamic libraries the bundle was linked with.
Enable C++ Container Overflow Checks for Address Sanitizer (CLANG_ADDRESS_SANITIZER_CONTAINER_OVERFLOW)
Check for C++ container overflow when Address Sanitizer is enabled. This check requires the entire application to be built with Address Sanitizer. If not, it may report false positives.
Allow Non-modular Includes In Framework Modules (CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES)
Enabling this setting allows non-modular includes to be used from within framework modules. This is inherently unsafe, as such headers might cause duplicate definitions when used by any client that imports both the framework and the non-modular includes.
Check for values stored to variables and never read again.
Check for misuses of the Grand Central Dispatch API.
Warn when a call to an NSLocalizedString() macro is missing a context comment for the localizer.
Warn when a nonlocalized string is passed to a user interface method expecting a localized string.
Warn about memory leaks, use-after-free, and other API misuses.
Check for misuses of nonnull parameter and return types.
Warn on nil pointers used as mutexes for @synchronized.
Warn if CF collections are created with non-pointer-size values. Check if NS collections are initialized with non-Objective-C-type elements.
Warn when an instance is improperly cleaned up in -dealloc.
Warn if a specialized generic type is converted to an incompatible type.
Warn about Objective-C method signatures with type incompatibilities.
Warn if functions accepting CFErrorRef or NSError cannot indicate that an error occurred.
Warn on leaks and improper reference count management.
Check that super init is properly called within an Objective-C initialization method.
Warn about private ivars that are never used.
EXPERIMENTAL Buffer overflows (CLANG_ANALYZER_SECURITY_BUFFER_OVERFLOW_EXPERIMENTAL)
Check for potential buffer overflows.
Warn on using a floating point value as a loop counter (CERT: FLP30-C, FLP30-CPP).
Warn on uses of getpw and gets. The functions are dangerous as they may trigger a buffer overflow.
Warn on uses of mktemp, which produces predictable temporary files. It is obsoleted by mktemps. Warn when mkstemp is passed fewer than 6 X's in the format string.
Warn on uses of rand, random, and related functions, which produce predictable random number sequences. Use arc4random instead.
Warn on uses of the strcpy and strcat functions, which can result in buffer overflows. Use strlcpy or strlcat instead.
Warn on uses of sensitive functions whose return values must be always checked.
Warn on uses of the vfork function, which is inherently insecure. Use the safer posix_spawn function instead.
Check for misuse of the Keychain Services API.
Choose a standard or non-standard C++ language dialect. Options include:
- C++98: Accept ISO C++ 1998 with amendments, but not GNU extensions.
-std=c++98 - GNU++98: Accept ISO C++ 1998 with amendments and GNU extensions.
-std=gnu++98 - C++11: Accept the ISO C++ 2011 standard with amendments, but not GNU extensions.
-std=c++11 - GNU++11: Accept the ISO C++ 2011 standard with amendments and GNU extensions.
-std=gnu++11 - C++14: Accept the ISO C++ 2014 standard with amendments, but not GNU extensions.
-std=c++14 - GNU++14: Accept the ISO C++ 2014 standard with amendments and GNU extensions.
-std=gnu++14 - Compiler Default: Tells the compiler to use its default C++ language dialect. This is normally the best choice unless you have specific needs. (Currently equivalent to GNU++98.)
Choose a version of the C++ standard library to use.
- libstdc++: A traditional C++ standard library that works with GCC and the LLVM Compiler (
default). - libc++: A highly optimized C++ standard library that works only with the LLVM Compiler, and is designed to support new C++11 features.
Toggles the amount of debug information emitted when debug symbols are enabled. This can impact the size of the generated debug information, which may matter in some cases for large projects, such as when using LTO.
Enables building with code coverage instrumentation. This is only used when the build has code coverage enabled, which is typically done via the Xcode scheme settings.
Enables the use of modules for system APIs. System headers are imported as semantic modules instead of raw headers. This can result in faster builds and project indexing.
When this setting is enabled, clang will use the shared debug info available in clang modules and precompiled headers. This results in smaller build artifacts, faster compile times, and more complete debug info. This setting should only be disabled when building static libraries with debug info for distribution.
Compiles reference-counted Objective-C code (when garbage collection is not enabled) to use Automatic Reference Counting. Code compiled using automated reference counting is compatible with other code (such as frameworks) compiled using either manual reference counting (for example, traditional retain and release messages) or automated reference counting. Using this mode is currently incompatible with compiling code to use Objective-C Garbage Collection.
Compiles Objective-C code to enable weak references for code compiled with manual retain release (MRR) semantics.
When linking a target using Objective-C code, implicitly link in Foundation (and if deploying back to an older OS) a backwards compatibility library to allow newer language features to run on an OS where the runtime support is not natively available. Most targets that use Objective-C should use this, although there are rare cases where a target should opt out of this behavior.
Add attribute annotations to properties and methods.
Infer instancetype for method result type instead of id.
Use NS_ENUM/NS_OPTIONS macros for enumerators.
Infer NS_DESIGNATED_INITIALIZER for designated initializer methods.
Enable migration to modern ObjC literals syntax.
Enable migration to modern ObjC subscripting syntax.
Choose the atomicity of the inferred properties.
Enable migration of setter/getter messages to property-dot syntax.
Infer protocol conformance from the interface methods.
Only modify public headers of a target.
Infer readonly properties from getter methods.
Infer readwrite properties from a getter and setter method.
Automatically link SDK frameworks that are referenced using #import or #include. This feature requires also enabling support for modules.
The path to the file of the profile data to use when Use Optimization Profile (CLANG_USE_OPTIMIZATION_PROFILE) is enabled.
The depth the static analyzer uses during the Build action. Use Deep to exercise the full power of the analyzer. Use Shallow for faster analysis.
The depth the static analyzer uses during the Analyze action. Use Deep to exercise the full power of the analyzer. Use Shallow for faster analysis.
When this setting is enabled, clang will use the optimization profile collected for a target when building it.
Warn about assigning integer constants to enum values that are out of the range of the enumerated type.
Warn about implicit conversions to boolean values that are suspicious. For example, writing if (foo) where foo is the name a function will trigger a warning.
Warn about implicit conversions of constant values that cause the constant value to change, either through a loss of precision, or entirely in its meaning.
When compiling C++ code using a language standard older than C++11, warn about the use of C++11 extensions.
Warn if an Objective-C class either subclasses a deprecated class or overrides a method that has been marked deprecated.
Warn about direct accesses to the Objective-C isa pointer instead of using a runtime API.
Warns about issues in documentation comments (doxygen-style) such as missing or incorrect documentation tags.
Warn about loop bodies that are suspiciously empty.
Warn about implicit conversions between different kinds of enum values. For example, this can catch issues when using the wrong enum flag as an argument to a function or method.
Warn about implicit integer conversions that change the signedness of an integer value.
Warn if all paths through a function call itself.
Warn about implicit conversions between pointers and integers. For example, this can catch issues when one incorrectly intermixes using NSNumber*'s and raw integers.
Warns when a nullable expression is used somewhere it’s not allowed, such as when passed as a _NONNULL parameter.
Warn about implicit ownership types on Objective-C object references as out parameters. For example, declaring a parameter with type NSObject** will produce a warning because the compiler will assume that the out parameter's ownership type is __autoreleasing.
Warn about @property declarations that are implicitly atomic.
Warn about implicit retains of self within blocks, which can create a retain-cycle.
Starting in Xcode 4.4, the Apple LLVM Compiler will implicitly synthesize properties that are not explicitly synthesized using @synthesize. This setting warns about such implicit behavior, even though the property is still synthesized. This is essentially a backwards compatibility warning, or for those who wish to continue to explicitly use @synthesize.
Warn about repeatedly using a weak reference without assigning the weak reference to a strong reference. This is often symptomatic of a race condition where the weak reference can become nil between accesses, resulting in unexpected behavior. Assigning to temporary strong reference ensures the object stays alive during the related accesses.
Warn about classes that unintentionally do not subclass a root class, such as NSObject.
Warn about various implicit conversions that can lose information or are otherwise suspicious.
Warn about suspicious uses of std::move.
Warns about potentially unreachable code.
Warn about using __bridge casts when not using ARC, where they have no effect.
Warn about declaring the same method more than once within the same @interface.
Warn about destructors for C++ objects that are called when an application is terminating.
Enables the use of extended vector instructions. Only used when targeting Intel architectures.
The path to a file specifying code-signing entitlements.
The name, also known as the common name, of a valid code-signing certificate in a keychain within your keychain path. A missing or invalid certificate will cause a build error.
Combines image files at different resolutions into one multi-page TIFF file that is HiDPI compliant for macOS 10.7 and later. Only image files in the same directory and with the same base name and extension are combined. The file names must conform to the naming convention used in HiDPI.
If enabled, PNG resource files are compressed as they are copied.
Identifies the build configuration, such as Debug or Release, that the target uses to generate the product.
The base path where build products will be placed during a build for a given configuration. By default, this is set to $(BUILD_DIR)/$(CONFIGURATION).
The base path where intermediates will be placed during a build for a given configuration. By default, this is set to $(PROJECT_TEMP_DIR)/$(CONFIGURATION).
Specifies the directory inside the generated bundle that contains the product’s files.
Causes the copying of resources to preserve resource forks and Finder info.
If enabled, headers are run through the unifdef(1) tool when copied to the product.
Specifies the flags to pass to unifdef(1) when invoking that tool to copy headers. This setting has no effect unless Run unifdef on Product Headers (COPY_HEADERS_RUN_UNIFDEF) is enabled.
Specifies whether binary files that are copied during the build, such as in a Copy Bundle Resources or Copy Files build phase, should be stripped of debugging symbols. It does not cause the linked product of a target to be stripped—use Strip Linked Product (STRIP_INSTALLED_PRODUCT) for that.
Other flags to pass to the C preprocessor when using the standalone C Preprocessor rule.
Implicitly include the given file when preprocessing using the standalone C Preprocessor rule. The path given should either be a project relative path or an absolute path.
Space-separated list of preprocessor macros of the form foo or foo=bar. These macros are used when preprocessing using the standalone C Preprocessor rule.
Enabling this setting will create a section in the product's linked binary containing the processed Info.plist file for the target. This setting only applies to command-line tool targets.
The name of the active architecture being processed.
This setting defines the current version of the project. The value must be a integer or floating point number, such as 57 or 365.8.
The name of the active variant being processed.
Activating this setting causes the -dead_strip flag to be passed to ld(1) via cc(1) to turn on dead code stripping. If this option is selected, -gfull (not -gused) must be used to generate debugging symbols in order to have them correctly stripped.
The type of debug information to produce.
- DWARF: Object files and linked products will use DWARF as the debug information format. dwarf
- DWARF with dSYM File: Object files and linked products will use DWARF as the debug information format, and Xcode will also produce a dSYM file containing the debug information from the individual object files (except that a dSYM file is not needed and will not be created for static library or object file products). dwarf-with-dsym
If enabled, the product will be treated as defining its own module. This enables automatic production of LLVM module map files when appropriate, and allows the product to be imported as a module.
If enabled, built products are placed in their installed locations in addition to the built products folder.
If enabled, indicates that binaries should be stripped and file mode, owner, and group information should be set to standard values.
Identifies the directory into which derived source files, such as those generated by lex and yacc, are placed.
The team ID of a development team to use for signing certificates and provisioning profiles.
This option controls the output of the distill tool.
This option controls the mode under which the distill tool is run—either it can regenerate its output entirely or it can incrementally edit the existing output.
Identifies the directory that contains the bundle’s documentation files.
The path at which all products will be rooted when performing an install build. For instance, to install your products on the system proper, set this path to /. Defaults to /tmp/$(PROJECT_NAME).dst to prevent a test install build from accidentally overwriting valid and needed data in the ultimate install path.
Typically this path is not set per target, but is provided as an option on the command line when performing an xcodebuild install. It may also be set in a build configuration in special circumstances.
Space-separated list of additional flags to pass to the dtrace compiler. Be sure to backslash-escape any arguments that contain spaces or special characters, such as path names that may contain spaces. Use this setting if Xcode does not already provide UI for a particular dtrace flag.
Determines the compatibility version of the resulting library, bundle, or framework binary. See Dynamic Library Design Guidelines in Dynamic Library Programming Topics for details on assigning version numbers of dynamic libraries.
This setting defines the current version of any framework built by the project. As with Current Project Version (CURRENT_PROJECT_VERSION), the value must be an integer or floating point number, such as 57 or 365.8. By default, it is set to $(CURRENT_PROJECT_VERSION). See Dynamic Library Design Guidelines in Dynamic Library Programming Topics for details on assigning version numbers of dynamic libraries.
Sets the base value for the internal "install path" (LC_ID_DYLIB) in a dynamic library. This will be combined with the EXECUTABLE_PATH to form the full install path. Setting Dynamic Library Install Name (LD_DYLIB_INSTALL_NAME) directly will override this setting. This setting defaults to the target's Installation Directory (INSTALL_PATH). It is ignored when building any product other than a dynamic library.
Embed all the built asset packs inside the product bundle. Since this negates the performance benefits of the On Demand Resources feature, it is only useful for testing purposes when it isn't practical to use an asset pack server.
Activating this setting indicates that the target or project should generate bitcode during compilation for platforms and architectures that support it. For Archive builds, bitcode will be generated in the linked binary for submission to the App Store. For other builds, the compiler and linker will check whether the code complies with the requirements for bitcode generation, but will not generate actual bitcode.
Specifies whether to automatically track dependencies on included header files.
Enabled the incremental distill option in the asset catalog compiler. This feature is experimental and should only be enabled with caution.
Controls whether assertion logic provided by NSAssert is included in the preprocessed source code or is elided during preprocessing. Disabling assertions can improve code performance.
Omit inapplicable resources when building for a single device. For example, when building for a device with a Retina display, exclude 1x resources.
If enabled, tagged assets—files and asset catalog entries—are built into asset packs based on their combination of tags. Untagged resources are treated normally.
Controls whether objc_msgSend calls must be cast to the appropriate function pointer type before being called.
When this setting is activated, the product will be built with options appropriate for running automated tests, such as making private interfaces accessible to the tests. This may result in tests running slower than they would without testability enabled.
This is a list of fnmatch()-style patterns of file or directory names to exclude when performing a recursive search. By default, this is set to .nib .lproj .framework .gch .xcode () .DS_Store CVS .svn .git .hg. Normally, if you override this value you should include the default values via the $(inherited) macro.
Identifies the directory that contains additional binary files.
This is the extension used for the executable product generated by the target, which has a default value based on the product type.
Identifies the directory that contains the binary the target builds.
Specifies the name of the binary the target produces.
Specifies the path to the binary the target produces within its bundle.
The prefix used for the executable product generated by the target, which has a default value based on the product type.
Specifies the suffix of the binary filename, including the character that separates the extension from the rest of the bundle name.
This is a project-relative path to a file that lists the symbols to export. See ld -exported_symbols_list for details on exporting symbols.
Specifies the directory that contains the product’s embedded frameworks.
This is a list of paths to folders containing frameworks to be searched by the compiler for both included or imported header files when compiling C, Objective-C, C++, or Objective-C++, and by the linker for frameworks used by the product. Paths are delimited by whitespace, so any paths with spaces in them must be properly quoted.
Framework bundles are versioned by having contents in subfolders of a version folder that has links to the current version and its contents.
Enabling this setting causes char to be unsigned by default, disabling it causes char to be signed by default.
Enable the CodeWarrior/Microsoft syntax for inline assembly code in addition to the standard GCC syntax.
Choose a standard or non-standard C language dialect.
-
ANSI C: Accept ISO C90 and ISO C++, turning off GNU extensions that are incompatible.
-ansiIncompatible GNU extensions include the asm, inline, and typeof keywords (but not the equivalent asm, inline, and typeof forms), and the // syntax for comments.
This setting also enables trigraphs.
-
C89: Accept ISO C90 (
1990), but not GNU extensions.-std=c89 -
GNU89: Accept ISO C90 and GNU extensions.
-std=gnu89 -
C99: Accept ISO C99 (
1999), but not GNU extensions.-std=c99 -
GNU99: Accept ISO C99 and GNU extensions.
-std=gnu99 -
C11: Accept ISO C11 (
2011), but not GNU extensions.-std=c11 -
GNU11: Accept ISO C11 and GNU extensions.
-std=gnu11 -
Compiler Default: Tells the compiler to use its default C language dialect. This is normally the best choice unless you have specific needs. (Currently equivalent to GNU99.)
Please see the full GCC manual for the full definition of all these settings on the C dialect.
Faster function calls for applications. Not appropriate for shared libraries, which need to be position-independent.
Controls whether asm, inline, and typeof are treated as keywords or whether they can be used as identifiers.
Controls whether built-in functions that do not begin with __builtin_ as prefix are recognized.
GCC normally generates special code to handle certain built-in functions more efficiently; for instance, calls to alloca may become single instructions that adjust the stack directly, and calls to memcpy may become inline copy loops. The resulting code is often both smaller and faster, but since the function calls no longer appear as such, you cannot set a breakpoint on those calls, nor can you change the behavior of the functions by linking with a different library. In addition, when a function is recognized as a built-in function, GCC may use information about that function to warn about problems with calls to that function, or to generate more efficient code, even if the resulting code still contains calls to that function. For example, warnings are given with -Wformat for bad calls to printf, when printf is built in, and strlen is known not to modify global memory.
Enable C++ exception handling. Generates extra code needed to propagate exceptions. For some targets, this implies GCC will generate frame unwind information for all functions, which can produce significant data size overhead, although it does not affect execution. If you do not specify this option, GCC will enable it by default for languages like C++ that normally require exception handling, and disable it for languages like C that do not normally require it. However, you may need to enable this option when compiling C code that needs to interoperate properly with exception handlers written in C++.
Enable generation of information about every class with virtual functions for use by the C++ runtime type identification features (dynamic_cast and typeid). If you don't use those parts of the language, you can save some space by using this flag. Note that exception handling uses the same information, but it will generate it as needed.
Enable exception handling. Generates extra code needed to propagate exceptions. For some targets, this implies GCC will generate frame unwind information for all functions, which can produce significant data size overhead, although it does not affect execution. If you do not specify this option, GCC will enable it by default for languages like C++ and Objective-C that normally require exception handling, and disable it for languages like C that do not normally require it. However, you may need to enable this option when compiling C code that needs to interoperate properly with exception handlers written in other languages. You may also wish to disable this option if you are compiling older programs that don't use exception handling.
Generate output containing library calls for floating point.
Activating this setting enables kernel development mode. This mode sets -static, -fno-common, -fno-cxa-atexit, -fno-exceptions, -fno-non-call-exceptions, -fapple-kext, -fno-weak, and -fno-rtti where applicable. This mode also sets -mno-altivec, -msoft-float, -fno-builtin and -mlong-branch for PowerPC targets.
This setting enables @try/@catch/@throw syntax for handling exceptions in Objective-C code. Only applies to Objective-C.
Recognize and construct Pascal-style string literals. Its use in new code is discouraged.
Pascal string literals take the form \pstring . The special escape sequence \p denotes the Pascal length byte for the string, and will be replaced at compile time with the number of characters that follow. The p may only appear at the beginning of a string literal, and may not appear in wide string literals or as an integral constant.
Specifies whether the binary uses the built-in functions that provide access to the SSE3 extensions to the IA-32 architecture.
Specifies whether the binary uses the built-in functions that provide access to the SSE4.1 extensions to the IA-32 architecture.
Specifies whether the binary uses the built-in functions that provide access to the SSE4.2 extensions to the IA-32 architecture.
Controls whether or not trigraphs are permitted in the source code.
Enables some floating point optimizations that are not IEEE754-compliant, but which usually work. Programs that require strict IEEE compliance may not work with this option.
Enables or disables generation of debug symbols. When debug symbols are enabled, the level of detail can be controlled by the Level of Debug Symbols build setting.
Activating this setting causes a notes file to be produced that the gcov code-coverage utility can use to show program coverage.
Enabling this option will enable increased sharing of precompiled headers among targets that share the same prefix header and precompiled header directory.
Xcode distinguishes between precompiled header (PCH) files by generating a hash value based on the command-line options to the compiler used to create the PCH. Enabling this option will exclude certain compiler options from that hash. Presently this option will exclude search path options (-I, -iquote, -isystem, -F, -L) from the hash.
Enabling increased sharing of PCH files carries some risk—if two targets use the same prefix header but have different include paths that cause the prefix header to include different files when they are precompiled, then subtle problems may result because one target will use a PCH that was built using files included by the other target. In this case, this option must be turned off in order to enforce correctness.
Inline Methods Hidden (GCC_INLINES_ARE_PRIVATE_EXTERN)
When enabled, out-of-line copies of inline methods are declared private extern.
Specifies whether to compile each source file according to its file type, or whether to treat all source files in the target as if they are of a specific language.
Activating this setting indicates that code should be added so program flow arcs are instrumented.
Enabling this option allows linking with the shared libraries. This is the default for most product types.
In C, allocate even uninitialized global variables in the data section of the object file, rather than generating them as common blocks. This has the effect that if the same variable is declared (without extern) in two different compilations, you will get an error when you link them.
Specifies the degree to which the generated code is optimized for speed and binary size.
-
None: Do not optimize.
-O0With this setting, the compiler's goal is to reduce the cost of compilation and to make debugging produce the expected results. Statements are independent—if you stop the program with a breakpoint between statements, you can then assign a new value to any variable or change the program counter to any other statement in the function and get exactly the results you would expect from the source code.
-
Fast: Optimizing compilation takes somewhat more time, and a lot more memory for a large function.
-O1With this setting, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time. In Apple's compiler, strict aliasing, block reordering, and inter-block scheduling are disabled by default when optimizing.
-
Faster: The compiler performs nearly all supported optimizations that do not involve a space-speed tradeoff.
-O2With this setting, the compiler does not perform loop unrolling or function inlining, or register renaming. As compared to the
Fastsetting, this setting increases both compilation time and the performance of the generated code. -
Fastest: Turns on all optimizations specified by the Faster setting and also turns on function inlining and register renaming options. This setting may result in a larger binary.
-O3\ -
Fastest, Smallest: Optimize for size: This setting enables all Faster optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
-Os -
Fastest, Aggressive Optimizations: This setting enables Fastest but also enables aggressive optimizations that may break strict standards compliance but should work well on well-behaved code.
-Ofast
Generates a precompiled header for the prefix header, which should reduce overall build times.
Note: Precompiling the prefix header will be most effective if the contents of the prefix header or any file it includes change rarely. If the contents of the prefix header or any file it includes change frequently, there may be a negative impact to overall build time.
Implicitly include the named header. The path given should either be a project relative path or an absolute path.
Space-separated list of preprocessor macros of the form foo or foo=bar.
Preprocessor Macros Not Used In Precompiled Headers (GCC_PREPROCESSOR_DEFINITIONS_NOT_USED_IN_PRECOMPS)
Space-separated list of preprocessor macros of the form foo or foo=bar. These macros are not used when precompiling a prefix header file.
Reuse string literals.
Make enums only as large as needed for the range of possible values.
WARNING: This setting generates code that may not binary compatible with code generated without this setting or with macOS frameworks.
Optimize code by making more aggressive assumptions about whether pointers can point to the same objects as other pointers. Programs that use pointers a lot may benefit from this, but programs that don't strictly follow the ISO C rules about the type with which an object may be accessed may behave unexpectedly.
Symbols Hidden by Default (GCC_SYMBOLS_PRIVATE_EXTERN)
When enabled, all symbols are declared private extern unless explicitly marked to be exported using attribute((visibility("default"))) in code. If not enabled, all symbols are exported unless explicitly marked as private extern. See Controlling Symbol Visibility in C++ Runtime Environment Programming Guide.
Emits extra code to use the routines specified in the C++ ABI for thread-safe initialization of local statics. You can disable this option to reduce code size slightly in code that doesn't need to be thread-safe.
Causes warnings about missing function prototypes to be treated as errors. Only applies to C and Objective-C.
Treat Incompatible Pointer Type Warnings as Errors (GCC_TREAT_INCOMPATIBLE_POINTER_TYPE_WARNINGS_AS_ERRORS)
Enabling this option causes warnings about incompatible pointer types to be treated as errors.
Enabling this option causes all warnings to be treated as errors.
Unrolls loops. Unrolling makes the code larger, but may make it faster by reducing the number of branches executed.
Controls whether the standard system directories are searched for header files. When disabled, only the directories you have specified with -I options (and the directory of the current file, if appropriate) are searched.
The compiler to use for C, C++, and Objective-C.
Warn if a value is implicitly converted from a 64-bit type to a 32-bit type.
Warn about the use of deprecated functions, variables, and types (as indicated by the deprecated attribute).
Unchecking this setting will suppress warnings from applying the offsetof macro to a non-POD type. According to the 1998 ISO C++ standard, applying offsetof to a non-POD type is undefined. In existing C++ implementations, however, offsetof typically gives meaningful results even when applied to certain kinds of non-POD types, such as a simple struct that fails to be a POD type only by virtue of having a constructor. This flag is for users who are aware that they are writing nonportable code and who have deliberately chosen to ignore the warning about it.
The restrictions on offsetof may be relaxed in a future version of the C++ standard.
Warn if a structure's initializer has some fields missing. For example, the following code would cause such a warning because x.h is implicitly zero:
```c
struct s { int f, g, h; };
struct s x = { 3, 4 };
```
This option does not warn about designated initializers, so the following modification would not trigger a warning:
```c
struct s { int f, g, h; };
struct s x = { `.f` = 3, `.g` = 4 };
```
Warn when a source file does not end with a newline.
Causes warnings to be emitted about missing prototypes.
Warn when pointers passed via arguments or assigned to a variable differ in sign.
Causes warnings to be emitted when a function with a defined return type (not void) contains a return statement without a return-value. Also emits a warning when a function is defined without specifying a return type.
Warn if methods required by a protocol are not implemented in the class adopting it. Only applies to Objective-C.
Warn whenever a switch statement has an index of enumeral type and lacks a case for one or more of the named codes of that enumeration. The presence of a default label prevents this warning. Case labels outside the enumeration range also provoke warnings when this option is used.
Warn about four-char literals (for example, macOS-style OSTypes: APPL).
Overloaded Virtual Functions (GCC_WARN_HIDDEN_VIRTUAL_FUNCTIONS)
Warn when a function declaration hides virtual functions from a base class.
For example, in the following example, the A class version of f() is hidden in B.
```c
struct A {
virtual void `f()`;
};
struct B: public A {
void `f(int)`;
};
```
As a result, the following code will fail to compile.
```c
B* b;
b->f();
```
This setting only applies to C++ and Objective-C++ sources.
Inhibit all warning messages.
Warn if an aggregate or union initializer is not fully bracketed. In the following example, the initializer for a is not fully bracketed, but the initializer for b is fully bracketed.
```c
int a`2``2` = { 0, 1, 2, 3 };
int b`2``2` = { { 0, 1 }, { 2, 3 } };
```
Warn if parentheses are omitted in certain contexts, such as when there is an assignment in a context where a truth value is expected, or when operators are nested whose precedence causes confusion. Also, warn about constructions where there may be confusion as to which if statement an else branch belongs. For example:
```c
{
if (`a`)
if (`b`)
foo ();
else
bar ();
}
```
In C, every else branch belongs to the innermost possible if statement, which in the example above is if (b). This is often not what the programmer expects, as illustrated by indentation used in the example above. This build setting causes GCC to issue a warning when there is the potential for this confusion. To eliminate the warning, add explicit braces around the innermost if statement so there is no way the else could belong to the enclosing if. For example:
```c
{
if (`a`)
{
if (`b`)
foo ();
else
bar ();
}
}
```
Warn when a class declares an nonvirtual destructor that should probably be virtual, because it looks like the class will be used polymorphically. This is only active for C++ or Objective-C++ sources.
Issue all the warnings demanded by strict ISO C and ISO C++; reject all programs that use forbidden extensions, and some other programs that do not follow ISO C and ISO C++. For ISO C, follows the version of the ISO C standard specified by any -std option used.
Hidden Local Variables (GCC_WARN_SHADOW)
Warn whenever a local variable shadows another local variable, parameter or global variable or whenever a builtin function is shadowed.
Warn when a comparison between signed and unsigned values could produce an incorrect result when the signed value is converted to unsigned.
Warn if multiple methods with differing argument and/or return types are found for a given selector when attempting to send a message using this selector to a receiver of type id or Class. When this setting is disabled, the compiler will omit such warnings if any differences found are confined to types that share the same size and alignment.
Check calls to printf and scanf to make sure that the arguments supplied have types appropriate to the format string specified, and that the conversions specified in the format string make sense.
Warn if a @selector(...) expression referring to an undeclared selector is found. A selector is considered undeclared if no method with that name has been declared before the @selector(...) expression, either explicitly in an @interface or @protocol declaration, or implicitly in an @implementation section. This option always performs its checks as soon as a @selector(...) expression is found, while -Wselector only performs its checks in the final stage of compilation. This also enforces the coding style convention that methods and selectors must be declared before being used.
Warn if a variable might be clobbered by a setjmp call or if an automatic variable is used without prior initialization.
Note: The compiler may not detect all cases where an automatic variable is initialized or all usage patterns that may lead to use prior to initialization. You can toggle between the normal uninitialized value checking or the more aggressive (conservative) checking, which finds more issues but the checking is much stricter.
Warn when a #pragma directive is encountered that is not understood by GCC. If this command line option is used, warnings will even be issued for unknown pragmas in system header files. This is not the case if the warnings were only enabled by the -Wall command-line option.
Warn whenever a static function is declared but not defined or a noninline static function is unused.
Warn whenever a label is declared but not used.
Warn whenever a function parameter is unused aside from its declaration.
Warn whenever a statement computes a result that is explicitly not used.
Warn whenever a local variable or nonconstant static variable is unused aside from its declaration.
Activating this setting will cause the object files built by a target to be prelinked using ld -r into a single object file, and that object file will then be linked into the final product. This is useful to force the linker to resolve symbols and link the object files into a single module before building a static library. Also, a separate set of link flags can be applied to the prelink allowing additional control over, for instance, exported symbols.
Forces the PkgInfo file to be written to wrapped products even if this file is not expected.
Activating this setting will cause the compiler and linker to generate profiling code. For example, GCC will generate code suitable for use with gprof(1).
Enables the generation of Text-Based stubs for dynamic libraries and frameworks.
Specifies whether the header map contains a name/path entry for every header in the target being built.
Specifies whether the header map contains a framework-name/path entry for every header in the target being built, including targets that do not build frameworks.
Specifies whether the header map contains a name/path entry for every header in the project, regardless of the headers’ target membership.
This is a list of paths to folders to be searched by the compiler for included or imported header files when compiling C, Objective-C, C++, or Objective-C++. Paths are delimited by whitespace, so any paths with spaces in them need to be properly quoted.
Instructs the XIB compiler to add custom fonts to the application's Info.plist, which will cause the fonts to activate upon application launch.
Show errors encountered during the compilation of XIB files.
If enabled, compile XIB files into flattened (non-wrapper) NIB files. After flattening, the resulting NIB is more compact but no longer editable by Interface Builder. When this option is disabled, the resulting NIB file remains editable in Interface Builder.
Defines the module name for Swift classes referenced without a specific module name.
Show notices encountered during the compilation of XIB files.
A list of additional flags to pass to the Interface Builder Compiler. Use this setting if Xcode does not already provide UI for a particular Interface Builder Compiler flag.
Instructs Interface Builder to load frameworks and Interface Builder plugins from the specified directory. Setting this value to $(BUILD_DIR)/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME) will ensure that Interface Builder will load frameworks and plug-ins from the built products directory of the current build configuration.
A list of paths to Interface Builder plugins to load when compiling XIB files.
A list of paths to be searched for Interface Builder plug-ins to load when compiling XIB files.
IBC_STRIP_NIBS
Show warnings encountered during the compilation of XIB files.
Instructs the Storyboard compiler to add custom fonts to the application's Info.plist that will cause the fonts to activate upon application launch.
Show errors encountered during the compilation of Storyboard files.
Compiles a Storyboard file into flattened (non-wrapper) Storyboard file. After flattening, the resulting Storyboard is more compact but no longer editable by Interface Builder. When this option is disabled, the resulting Storyboard file remains editable in Interface Builder.
Defines the module name for Swift classes referenced without a specific module name.
Show notices encountered during the compilation of Storyboard files.
A list of additional flags to pass to the Interface Builder Compiler. Use this setting if Xcode does not already provide UI for a particular Interface Builder Compiler flag.
IBSC_STRIP_NIBS
Show warnings encountered during the compilation of Storyboard files.
This is a list of fnmatch()-style patterns of file or directory names to include when performing a recursive search. By default, this list is empty and is only customized when you want to provide exceptions to the list of filename patterns provided in Sub-Directories to Exclude in Recursive Searches (EXCLUDED_RECURSIVE_SEARCH_PATH_SUBDIRECTORIES).
Expand build settings in the Info.plist file.
The project-relative path to the property list file that contains the Info.plist information used by bundles. For details on information property list files, see Information Property List Files in Runtime Configuration Guidelines.
Other flags to pass to the C preprocessor when preprocessing the Info.plist file.
Specifies the output encoding for the output Info.plist. The output encodings can be binary or XML. By default, the output encoding will be unchanged from the input.
Specifies the path to the bundle’s information property list file.
Implicitly include the given file when preprocessing the Info.plist file. The path given should either be a project relative path or an absolute path.
Preprocess the Info.plist file using the C Preprocessor.
Space-separated list of preprocessor macros of the form foo or foo=bar. These macros are used when preprocessing the Info.plist file.
Specifies the file that contains the bundle’s localized strings file.
This is the name of the routine to use for initialization.
Enables private framework inlining for Text-Based Stubs.
Specifies whether the target’s Copy Files build phases are executed in install-header builds.
Specifies whether the target’s Run Script build phases are executed in install-header builds. See Active Build Action (ACTION) for details on install-header builds.
Identifies the directory in the developer’s filesystem into which the installed product is placed.
The group name or gid for installed products.
Permissions used for installed product files.
The owner name or uid for installed products.
The directory in which to install the build products. This path is prepended by the Installation Build Products Location (DSTROOT).
Activating this setting will preserve private external symbols, rather than turning them into static symbols. This setting is also respected when performing a single-object prelink.
This setting defines the path to which the linker should emit information about what files it used as inputs and generated. Xcode uses this information for its dependency tracking. Setting the value of this setting to empty will disable passing this option to the linker.
Sets an internal install path (LC_ID_DYLIB) in a dynamic library. Any clients linked against the library will record that path as the way dyld should locate this library. If this option is not specified, then the -o path will be used. This setting is ignored when building any product other than a dynamic library. See Dynamic Library Programming Topics.
Activating this setting will cause the linker to write a map file to disk, which details all symbols and their addresses in the output image. The path to the map file is defined by the Path to Link Map File (LD_MAP_FILE_PATH) setting.
This setting defines the path to the map file written by the linker when the Write Link Map File (LD_GENERATE_MAP_FILE) setting is activated. By default, a separate file will be written for each architecture and build variant, and these will be generated in the Intermediates directory for the target whose product is being linked.
Activating this setting will prevent Xcode from building a main executable that is position independent (PIE). When targeting macOS 10.7 or later, PIE is the default for main executables, so activating this setting will change that behavior. When targeting OS X10.6 or earlier, or when building for i386, PIE is not the default, so activating this setting does nothing.
You cannot create a PIE from .o files compiled with -mdynamic-no-pic. Using PIE means the codegen is less optimal, but the address randomization adds some security.
This setting controls whether arguments to the linker should be quoted using -Xlinker. By default, Xcode invokes the linker by invoking the driver of the compiler used to build the source files in the target, and passing -Xlinker to quote arguments will cause the compiler driver to pass them through to the linker (rather than trying to evaluate them within the driver). By default, this setting is enabled. Disabling it will cause Xcode to not use -Xlinker to pass arguments to the linker. Disabling this setting is useful if the target has instructed Xcode to use an alternate linker (for example, by setting the LD setting to the path to another linker) and that alternate linker does not recognize -Xlinker.
This is a list of paths to be added to the runpath search path list for the image being created. At runtime, dyld uses the runpath when searching for dylibs whose load path begins with @rpath/. See Dynamic Library Programming Topics.
Space-separated list of additional flags to pass to lex. Be sure to backslash-escape any arguments that contain spaces or special characters, such as path names that may contain spaces. Use this setting if Xcode does not already provide UI for a lex flag.
Enabling this option causes lex to generate a case-insensitive scanner. The case of letters given in the lex input patterns will be ignored, and tokens in the input will be matched regardless of case. The matched text given in yytext will have the preserved case (for example, it will not be folded).
Enabling this option instructs lex to insert #line directives so error messages in the actions will be correctly located with respect to either the original lex input file (if the errors are due to code in the input file), or lex.yy.c (if the errors are lex's fault). This option is enabled by default; disabling it passes a flag to lex to not insert #line directives.
Enabling this option causes the default rule (that unmatched scanner input is echoed to stdout) to be suppressed. If the scanner encounters input that does not match any of its rules, it aborts with an error. This option is useful for finding holes in a scanner's rule set.
Enabling this option causes lex to suppress its warning messages.
This is a list of paths to folders to be searched by the linker for libraries used by the product. Paths are delimited by whitespace, so any paths with spaces in them need to be properly quoted.
Activating this setting causes the linker to display mangled names for C++ symbols. Normally, this is not recommended, but turning it on can help to diagnose and solve C++ link errors.
When this setting is enabled, the compiler driver will automatically pass its standard libraries to the linker to use during linking. If desired, this flag can be used to disable linking with the standard libraries, and then individual libraries can be passed as Other Linker Flags (OTHER_LDFLAGS).
Enabling this setting allows optimization across file boundaries during linking.
- No: Disabled. Do not use link-time optimization.
- Monolithic Link-Time Optimization: This mode performs monolithic link-time optimization of binaries, combining all executable code into a single unit and running aggressive compiler optimizations.
- Incremental Link-Time Optimization: This mode performs partitioned link-time optimization of binaries, inlining between compilation units and running aggressive compiler optimizations on each unit in parallel. This enables fast incremental builds and uses less memory than Monolithic LTO.
This setting determines the format of the produced binary and how it can be linked when building other binaries. For information on binary types, see Building Mach-O Files in Mach-O Programming Topics.
- Executable: Executables and standalone binaries and cannot be linked. mh_execute
- Dynamic Library: Dynamic libraries are linked at build time and loaded automatically when needed. mh_dylib
- Bundle: Bundle libraries are loaded explicitly at run time. mh_bundle
- Static Library: Static libraries are linked at build time and loaded at execution time. staticlib
- Relocatable Object File: Object files are single-module files that are linked at build time. mh_object
Code will load on this and later versions of macOS. Framework APIs that are unavailable in earlier versions will be weak-linked; your code should check for null function pointers or specific system versions before calling newer APIs.
Compile .xcmappingmodel files into .cdm without reporting warnings.
This is the project-relative path to the LLVM module map file that defines the module structure for the compiler. If empty, it will be automatically generated for appropriate products when Defines Module (DEFINES_MODULE) is enabled.
This is the project-relative path to the LLVM module map file that defines the module structure for private headers.
Absolute path of folder in which compiler stores its cached modules—this cache is a performance improvement.
This is the identifier of the kernel module listed in the generated stub. This is only used when building kernel extensions.
This defines the name of the kernel module start routine. This is only used when building kernel extensions.
This defines the name of the kernel module stop routine. This is only used when building kernel extensions.
This is the version of the kernel module listed in the generated stub. This is only used when building kernel extensions.
Suppress managed object model compiler (momc) warnings for delete rules during the compilation of .xcdatamodel(d) files.
Suppress managed object model compiler (momc) warnings from output on missing inverse relationships during the compilation of .xcdatamodel(d) files
Suppress momc warnings for entities with more than 100 properties (MOMC_NO_MAX_PROPERTY_COUNT_WARNINGS)
Suppress managed object model compiler (momc) warnings from output on entities with more than 100 properties during the compilation of .xcdatamodel(d) files.
Suppress managed object model compiler (momc) warnings from output during the compilation of .xcdatamodel(d) files
Suppress managed object model compiler (momc) warnings from output on transient inverse relationships during the compilation of .xcdatamodel(d) files. This is only intended to be used on 10.4.x created models that compiled properly in 10.4.x before the error was introduced in 10.5
Space-separated list of additional flags to pass to the nasm assembler. Be sure to backslash-escape any arguments that contain spaces or special characters, such as path names that may contain spaces. Use this setting if Xcode does not already provide UI for a particular nasm flag.
Specifies a file to be preincluded, before the main source file starts to be processed.
Identifies the architecture on which the build is being performed.
Partially identifies the directory into which variant object files are placed. The complete specification is computed using the variants of this build setting.
The path where intermediate files will be placed during a build. Intermediate files include generated sources, object files, etc. Shell script build phases can place and access files here, as well. Typically this path is not set per target, but is set per project or per user. By default, this is set to $(PROJECT_DIR)/build.
If enabled, only the active architecture is built.
Defined a set of initial On Demand Resources tags to be downloaded and installed with your application.
Once your app is installed, this defined a set of On Demand Resources tags that should be downloaded. These tags are downloaded after the initial installation of your application, and will be downloaded in the order the tags provided in the list from first to last.
A list of the architectures for which the product will be built. This is usually set to a predefined build setting provided by the platform.
Auto-vectorizes the OpenCL kernels for the CPU. This setting takes effect only for the CPU. This makes it possible to write a single kernel that is portable and performant across CPUs and GPUs.
The OpenCL C compiler version supported by the platform.
This option controls how single precision and double precision denormalized numbers are handled. If specified as a build option, the single precision denormalized numbers may be flushed to zero; double precision denormalized numbers may also be flushed to zero if the optional extension for double precision is supported. This is intended to be a performance hint and the OpenCL compiler can choose not to flush denorms to zero if the device supports single precision (or double precision) denormalized numbers.
This option is ignored for single precision numbers if the device does not support single precision denormalized numbers, for example, CL_FP_DENORM bit is not set in CL_DEVICE_SINGLE_FP_CONFIG.
This option is ignored for double precision numbers if the device does not support double precision or if it does support double precision but not double precision denormalized numbers, for example, CL_FP_DENORM bit is not set in CL_DEVICE_DOUBLE_FP_CONFIG.
This flag only applies for scalar and vector single precision floating-point variables and computations on these floating-point variables inside a program. It does not apply to reading from or writing to image objects.
Treat double precision floating-point expression as a single precision floating-point expression. This option is available for GPUs only.
This allows optimizations for floating-point arithmetic that may violate the IEEE 754 standard and the OpenCL numerical compliance requirements defined in in section 7.4 for single-precision floating-point, section 9.3.9 for double-precision floating-point, and edge case behavior in section 7.5 of the OpenCL 1.1 specification.
This is intended to be a performance optimization.
This option causes the preprocessor macro FAST_RELAXED_MATH to be defined in the OpenCL program.
Allow a * b + c to be replaced by a mad instruction. The mad computes a * b + c with reduced accuracy. For example, some OpenCL devices implement mad as truncate the result of a * b before adding it to c.
This is intended to be a performance optimization.
-
None: Do not optimize.
-O0With this setting, the compiler's goal is to reduce the cost of compilation and to make debugging produce the expected results. Statements are independent—if you stop the program with a breakpoint between statements, you can then assign a new value to any variable or change the program counter to any other statement in the function and get exactly the results you would expect from the source code.
-
Fast: Optimizing compilation takes somewhat more time, and a lot more memory for a large function.
-O,-O1With this setting, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time. In Apple's compiler, strict aliasing, block reordering, and inter-block scheduling are disabled by default when optimizing.
-
Faster: The compiler performs nearly all supported optimizations that do not involve a space-speed tradeoff.
-O2With this setting, the compiler does not perform loop unrolling or function inlining, or register renaming. As compared to the Fast setting, this setting increases both compilation time and the performance of the generated code.
-
Fastest: Turns on all optimizations specified by the Faster setting and also turns on function inlining and register renaming options. This setting may result in a larger binary.
-O3 -
Fastest, smallest: Optimize for size. This setting enables all Faster optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
-Os
Space-separated list of additional flags to pass to the compiler. Be sure to backslash-escape any arguments that contain spaces or special characters, such as path names that may contain spaces. Use this setting if Xcode does not already provide UI for a particular compiler flag.
Space-separated list of preprocessor macros of the form foo or foo=bar.
The path to a file that alters the order in which functions and data are laid out.
For each section in the output file, any symbol in that section that are specified in the order file is moved to the start of its section and laid out in the same order as in the order file. Order files are text files with one symbol name per line. Lines starting with a # are comments. A symbol name may be optionally preceded with its object file leafname and a colon (for example, foo.o:_foo). This is useful for static functions/data that occur in multiple files. A symbol name may also be optionally preceded with the architecture (for example, ppc:_foo or ppc:foo.o:_foo). This enables you to have one order file that works for multiple architectures. Literal c-strings may be ordered by quoting the string in the order file (for example, "Hello, world\n").
Generally you should not specify an order file in Debug or Development configurations, as this will make the linked binary less readable to the debugger. Use them only in Release or Deployment configurations.
Saves the output script in execute-only form; the script can be run, but cannot be opened in Script Editor or Xcode. With this option turned off, a user may see the original script source by opening the script.
Space-separated list of additional flags to pass to the compiler for C and Objective-C files. Be sure to backslash-escape any arguments that contain spaces or special characters, such as path names that may contain spaces. Use this setting if Xcode does not already provide UI for a particular C or Objective-C compiler flag.
A list of additional options to pass to codesign(1).
Space-separated list of additional flags to pass to the compiler for C++ and Objective-C++ files. Be sure to backslash-escape any arguments that contain spaces or special characters, such as path names that may contain spaces. Use this setting if Xcode does not already provide UI for a C++ or Objective-C++ compiler flag.
Options defined in this setting are passed to invocations of the linker.
Options defined in this setting are passed to all invocations of the archive librarian, which is used to generate static libraries.
Space-separated list of additional flags to pass to mig. Be sure to backslash-escape any arguments that contain spaces or special characters, such as path names that may contain spaces. Use this setting if Xcode does not already provide UI for a mig flag.
Space-separated list of additional flags to pass to osacompile. Be sure to backslash-escape any arguments that contain spaces or special characters, such as path names that may contain spaces. Use this setting if Xcode does not already provide UI for a particular osacompile flag.
Space-separated list of additional flags to pass to the Rez compiler. Be sure to backslash-escape any arguments that contain spaces or special characters, such as path names that may contain spaces. Use this setting if Xcode does not already provide UI for a particular Rez flag.
A list of additional flags to pass to the Swift compiler.
Options defined in this setting are passed to invocations of the text-base InstallAPI tool.
Uniform type identifier. Identifies the type of the product the target builds. Some products may be made up of a single binary or archive. Others may comprise several files, which are grouped under a single directory. These container directories are known as bundles.
Specifies the output encoding for property list files (.plist). The output endcodings can be binary or XML. By default, the output encoding will be unchanged from the input.
Specifies the directory that contains the product’s plugins.
Precompiled Header Uses Files From Build Directory (PRECOMPS_INCLUDE_HEADERS_FROM_BUILT_PRODUCTS_DIR)
This setting allows for better control of sharing precompiled prefix header files between projects. By default, Xcode assumes that the prefix header file may include header files from the build directory if the build directory is outside of the project directory. Xcode cannot determine this ahead of time since other projects may not have been built into the shared build directory at the time the information is needed.
If your prefix file never includes files from the build directory you may set this to NO to improve sharing of precompiled headers. If the prefix does use files from a build directory that is inside your project directory, you may set this to YES to avoid unintended sharing that may result in build failures.
Additional flags to pass when performing a single-object prelink.
Additional libraries to pass when performing a single-object prelink.
Activating this setting, in combination with the Dead Code Stripping (DEAD_CODE_STRIPPING) (-dead_strip) option, causes the -no_dead_strip_inits_and_terms flag to be passed to ld(1) via cc(1) to disable dead code stripping for initialization and termination routines. This option should not be used without the aforementioned Dead Code Stripping (DEAD_CODE_STRIPPING) option.
The location to copy the private headers to during building, relative to the built products folder.
A string that uniquely identifies the bundle. The string should be in reverse DNS format using only alphanumeric characters (A-Z, a-z, 0-9), the dot (.), and the hyphen (-). This value is used as the CFBundleIdentifier in the Info.plist of the built bundle.
Path to a file specifying additional requirements for a product archive.
The name to use for the source code module constructed for this target, and which will be used to import the module in implementation source files. Must be a valid identifier.
This is the basename of the product generated by the target.
The name of the current project.
Identifies the directory in which the project’s intermediate build files are placed. This directory is shared between all the targets defined by the project. Run Script build phases should generate intermediate build files in the directory identified by DERIVED_FILE_DIR, not the location this build setting specifies.
The UUID of a valid provisioning profile. A missing or invalid profile will cause a build error.
This build setting is deprecated. Use Provisioning Profile (PROVISIONING_PROFILE_SPECIFIER) instead.
Must contain a profile name or UUID. A missing or invalid profile will cause a build error. Use in conjunction with DEVELOPMENT_TEAM to fully specify provisioning profile.
The location to copy the public headers to during building, relative to the built products folder.
List of framework names that should have their symbols be reexported from the built library.
List of library names that should have their symbols be reexported from the built library.
List of library paths that should have their symbols be reexported from the built library.
Specifies whether to remove CVS directories from bundle resources when they are copied.
Specifies whether to remove .git directories from bundle resources when they are copied.
Specifies whether to remove .hg directories from bundle resources when they are copied.
Specifies whether to remove SVN directories from bundle resources when they are copied.
Determines whether ResMerger treats binary input files as data-fork hosted or resource-fork hosted, or whether it automatically examines each input file.
Overrides Targeted Device Family (TARGETED_DEVICE_FAMILY) when the resource copying needs to differ from the default targeted device.
Specifies whether to keep copies of unstripped binaries available.
Specifies the directory in which the collected Resource Manager resources generated by ResMerger are stored before they are added to the product.
Specifies the directory in which compiled Resource Manager resources generated by Rez are stored before they are collected using ResMerger.
Implicitly include the named file on the command line for each Rez file compiled. The path given should either be a project relative path or an absolute path.
These strings will be defined when compiling resource manager resources.
These strings will be undefined when compiling resource manager resources.
Enables aliases to be unresolved or conditionally resolved. The default is to resolve aliases always.
Enabling this option causes the resource map output to be read-only.
Enables the recognition of a specific 2-byte character script identifier to use when compiling resource manager resources. This allows for 2-byte characters in strings to be handled as indivisible entities. The default language is Roman, which specifies 1-byte character sets.
This is a list of paths to search for files with resource manager resources. Paths are delimited by whitespace, so any paths with spaces in them need to be properly quoted.
Enabling this option causes version and progress information to be written when compiling resource manager resources.
Enabling this option causes warnings about redeclared resource types to be suppressed.
Activating this setting will cause Xcode to run the Clang static analysis tool on qualifying source files during every build.
Activating this setting will cause all source files to be scanned for includes (for example, of header files) when computing the dependency graph, in which case if an included file is changed then the including file will be rebuilt next time a target containing it is built. Normally only certain types of files, such as C-language source files, are scanned.
This setting is useful if your project contains files of unusual types, which are compiled using a custom build rule.
Specifies the directory that contains the product’s scripts.
The name or path of the base SDK being used during the build. The product will be built against the headers and libraries located inside the indicated SDK. This path will be prepended to all search paths, and will be passed through the environment to the compiler and linker. Additional SDKs can be specified in the Additional SDKs (ADDITIONAL_SDKS) setting.
These flags are typically used to specify options for ordering symbols within segments, for example the -sectorder option to ld.
Generally you should not specify symbol ordering options in Debug or Development configurations, as this will make the linked binary less readable to the debugger. Use them only in Release or Deployment configurations.
Activating this setting when the linked product is to be stripped will cause stripping to occur via a separate invocation of strip(1). Otherwise stripping will occur during linking, if possible.
Activating this setting when the linked product's symbols are to be edited will cause editing to occur via a separate invocation of nmedit(1). Otherwise editing will occur during linking, if possible.
Specifies the directory that contains the product’s shared frameworks.
The path where precompiled prefix header files are placed during a build. Defaults to $(OBJROOT)/SharedPrecompiledHeaders. Using a common location allows precompiled headers to be shared between multiple projects.
If enabled, don't install built products even if deployment locations are active.
Identifies the directory containing the target’s source files.
Specify the encoding to be used for Strings files (by default, the output encoding will be 16-bit Unicode). The value can be either an NSStringEncoding, such as one of the numeric values recognized by NSString, or it can be an IANA character set name as understood by CFString. The operation will fail if the file cannot be converted to the specified encoding.
Additional flags to be passed when stripping the linked product of the build.
If enabled, the linked product of the build will be stripped of symbols when performing deployment postprocessing.
Metadata in the form of text chunks in PNG files will be removed to reduce their footprint on disk.
The level of symbol stripping to be performed on the linked product of the build. The default value is defined by the target's product type.
- All Symbols: Completely strips the binary, removing the symbol table and relocation information. all,
-s - Non-Global Symbols: Strips non-global symbols, but saves external symbols. non-global,
-x - Debugging Symbols: Strips debugging symbols, but saves local and global symbols. debugging,
-S
The list of supported platforms from which a base SDK can be used. This setting is used if the product can be built for multiple platforms using different SDKs.
Enable to indicate that the target supports Text-Based InstallAPI, which will enable its generation during install builds.
A list of compilation conditions to enable for conditional compilation expressions.
Disable runtime safety checks when optimizing.
A list of paths to be searched by the Swift compiler for additional Swift modules.
For frameworks, install the Objective-C compatibility header describing bridged Swift classes into the Public Headers Folder Path (PUBLIC_HEADERS_FOLDER_PATH) so they may be accessed from Objective-C code using the framework. Defaults to YES.
Path to the header defining the Objective-C interfaces to be exposed in Swift.
Name to use for the header that is generated by the Swift compiler for use in #import statements in Objective-C.
- None: Compile without any optimization.
-Onone - Fast, Single-File Optimization:-O
- Fast, Whole Module Optimization:-O
-whole-module-optimization
This setting controls the level of reflection metadata the Swift compiler emits.
- All: Type information about stored properties of Swift structs and classes, Swift enum cases, and their names, are emitted into the binary for reflection and analysis in the Memory Graph Debugger.
- Without Names: Only type information about stored properties and cases are emitted into the binary, with their names omitted.
-disable-reflection-names - None: No reflection metadata is emitted into the binary. Accuracy of detecting memory issues involving Swift types in the Memory Graph Debugger will be degraded and reflection in Swift code may not be able to discover children of types, such as properties and enum cases.
-disable-reflection-metadata
Don't emit any warnings.
Treat all warnings as errors.
The path at which all products will be placed when performing a build. Typically this path is not set per target, but is set per-project or per-user. By default, this is set to $(PROJECT_DIR)/build.
Selects the level of warnings and errors to report when building Text-Based InstallAPI.
The build system uses the selected device to set the correct value for the UIDeviceFamily key it adds to the target's Info.plist file.
Identifies the root of the directory hierarchy that contains the product’s files (no intermediate build files). Run Script build phases that operate on product files of the target that defines them should use the value of this build setting, but Run Script build phases that operate on product files of other targets should use BUILT_PRODUCTS_DIR instead.
The name of the current target.
Identifies the directory containing the target’s intermediate build files. Run Script build phases should place intermediate files at the location indicated by DERIVED_FILE_DIR, not the directory identified by this build setting.
Path to the executable into which a bundle of tests is injected. Only specify this setting if testing an application or other executable.
If provided and Text-Based InstallAPI is enabled, the path to a file to use as the Text-Based InstallAPI for the product instead of generating the API from the installed header content.
When running tests that measure performance via XCTestCase, report missing baselines as test failures.
A project-relative path to a file that lists the symbols not to export. See ld -exported_symbols_list for details on exporting symbols.
Specifies the directory that contains the product’s unlocalized resources.
This is a list of paths to folders to be searched by the compiler for included or imported user header files (those headers listed in quotes) when compiling C, Objective-C, C++, or Objective-C++. Paths are delimited by whitespace, so any paths with spaces in them need to be properly quoted. See Always Search User Paths (ALWAYS_SEARCH_USER_PATHS) for more details on how this setting is used. If the compiler doesn't support the concept of user headers, then the search paths are prepended to the any existing header search paths defined in Header Search Paths (HEADER_SEARCH_PATHS).
Enable the use of Header Maps, which provide the compiler with a mapping from textual header names to their locations, bypassing the normal compiler header search path mechanisms. This allows source code to include headers from various locations in the file system without needing to update the header search path build settings.
If enabled, perform validation checks on the product as part of the build process.
A space-separated list of architectures for which the target should actually be built. For each target, this list is intersected with the list specified in Architectures (ARCHS), and the resulting set is built. This allows individual targets to opt out of building for particular architectures. If the resulting set of architectures is empty, no executable will be produced.
Specifies whether the target’s Copy Files build phases generate additional information when copying files.
Selects the process used for version-stamping generated files.
- None: Use no versioning system.
- Apple Generic: Use the current project version setting. apple-generic
This defines a reference to the user performing a build to be included in the generated Apple Generic Versioning stub. Defaults to the value of the USER environment variable.
This defines a prefix string for the version info symbol declaration in the generated Apple Generic Versioning stub. This can be used, for example, to add an optional export keyword to the version symbol declaration. This should rarely be changed.
Used to specify a name for the source file that will be generated by Apple Generic Versioning and compiled into your product. By default, this is set to $(PRODUCT_NAME)_vers.c.
Used as a prefix for the name of the version info symbol in the generated versioning source file. If you prefix your exported symbols you will probably want to set this to the same prefix.
Used as a suffix for the name of the version info symbol in the generated versioning source file. This is rarely used.
Space-separated list of additional warning flags to pass to the compiler. Use this setting if Xcode does not already provide UI for a particular compiler warning flag.
These flags are passed with linker invocations, and by default give the -no_arch_warnings flag to the linker to avoid many warnings being generated during multi-architecture builds.
The extension used for product wrappers, which has a default value based on the product type.
Specifies the filename, including the appropriate extension, of the product bundle.
Specifies the suffix of the product bundle name, including the character that separates the extension from the rest of the bundle name.
Append compiled plug-in data to existing plug-in data, instead of overwriting it.
Copy original (uncompiled) plugin data to output alongside compiled plug-in data.
Include extension XML data in the resulting .xcplugindata files.
The property list format, binary or XML, to use for the resulting .xcplugindata file.
Latest version of Developer Tools on which this plugin will be used.
Earliest version of Developer Tools on which this plugin will be used.
Space-separated list of additional flags to pass to yacc. Be sure to backslash-escape any arguments that contain spaces or special characters, such as path names that may contain spaces. Use this setting if Xcode does not already provide UI for a yacc flag.
The file stem to use for the files generated by yacc. The files will be named <stem>.tab.c and <stem>.tab.h based on the value of this setting. The Standard (y) option will cause all yacc source files in the same target to produce the same output file, and it is not recommended for targets containing multiple yacc source files.
Enabling this option changes the preprocessor directives generated by yacc so that debugging statements will be incorporated in the compiled code.
Enabling this option causes yacc to insert the #line directives in the generated code. The #line directives let the C compiler relate errors in the generated code to the user's original code. If this option is disabled, #line directives specified by the user in the source file will still be retained.