Specifies one or more option specifications that are merged with the inputs when applicable. The parameter can be used to indirectly specify various compilation arguments independent of the actual inputs. This is generally useful when common options need to be specified to multiple compilation inputs. When compilation arguments are determined, each option specification will be merged into the used argumnets if applicable. An option is considered to be applicable to merging if all of the Identifier parts are contained in the compilation task Identifier, and the Language arguments can be matched. In case of unresolveable merge conflicts, the task will throw an appropriate exception.

The Identifier of the compilation. Each compilation task has an identifier that uniquely identifies it during a build execution. The identifier is used to determine the output directory of the compilation. It is also used to merge the appropriate options specified in CompilerOptions parameter. An identifier constists of dash separated parts of character sequences of a-z, A-Z, 0-9, _, ., (), [], @. An option specification in the CompilerOptions can be merged if the compilation identifier contains all parts of the option Identifier. If not specified, the identifier is determined based on the current working directory, or assigned to "default", however, it won't be subject to option merging.

Specifies one or more inputs for the compilation. The inputs may be either simple paths, wildcards, file locations, file collections or complex configuration specifying the input source files passed to the backend compiler. If not specified, the compilation language will be determined based on the extension of an input file. If the file extension ends with "pp" or "xx", C++ is used. Objective-C is used for the "m" extension, and Objective-C++ for "mm". In any other cases, the file is compiled for the C language.

Specifies the SDKs (Software Development Kits) used by the task. SDKs represent development kits that are available in the build environment and to the task. SDKs are used to determine the appropriate build environment to execute the task, as well to resolve paths against them (e.g. IncludeDirectory, LibraryPath). The "Clang" SDK is used to determine the location of the clang executable. If it is not specified, then the task will attempt to determine it automatically.