OXIESEC PANEL

Name	Size	Modified	Perms
📁 ..	-	04/04/2023 07:10:48 PM	rwxr-xr-x
📄 ccmake.1.html	44.19 KB	04/04/2023 07:05:08 PM	rw-r--r--
📄 cmake-buildsystem.7.html	161.14 KB	04/04/2023 07:05:09 PM	rw-r--r--
📄 cmake-commands.7.html	21.66 KB	04/04/2023 07:05:09 PM	rw-r--r--
📄 cmake-compile-features.7.html	46.17 KB	04/04/2023 07:05:09 PM	rw-r--r--
📄 cmake-configure-log.7.html	35.93 KB	04/04/2023 07:05:09 PM	rw-r--r--
📄 cmake-developer.7.html	60.56 KB	04/04/2023 07:05:09 PM	rw-r--r--
📄 cmake-env-variables.7.html	15.36 KB	04/04/2023 07:05:09 PM	rw-r--r--
📄 cmake-file-api.7.html	174.79 KB	04/04/2023 07:05:10 PM	rw-r--r--
📄 cmake-generator-expressions.7.html	229.68 KB	04/04/2023 07:05:11 PM	rw-r--r--
📄 cmake-generators.7.html	16.07 KB	04/04/2023 07:05:11 PM	rw-r--r--
📄 cmake-gui.1.html	27.62 KB	04/04/2023 07:05:11 PM	rw-r--r--
📄 cmake-language.7.html	67.9 KB	04/04/2023 07:05:11 PM	rw-r--r--
📄 cmake-modules.7.html	37.63 KB	04/04/2023 07:05:11 PM	rw-r--r--
📄 cmake-packages.7.html	84.94 KB	04/04/2023 07:05:11 PM	rw-r--r--
📄 cmake-policies.7.html	48.41 KB	04/04/2023 07:05:11 PM	rw-r--r--
📄 cmake-presets.7.html	122.21 KB	04/04/2023 07:05:12 PM	rw-r--r--
📄 cmake-properties.7.html	80.47 KB	04/04/2023 07:05:12 PM	rw-r--r--
📄 cmake-qt.7.html	47.92 KB	04/04/2023 07:05:12 PM	rw-r--r--
📄 cmake-server.7.html	5.39 KB	04/04/2023 07:05:12 PM	rw-r--r--
📄 cmake-toolchains.7.html	92.74 KB	04/04/2023 07:05:12 PM	rw-r--r--
📄 cmake-variables.7.html	105.71 KB	04/04/2023 07:05:12 PM	rw-r--r--
📄 cmake.1.html	170.8 KB	04/04/2023 07:05:13 PM	rw-r--r--
📄 cpack-generators.7.html	7.54 KB	04/04/2023 07:05:13 PM	rw-r--r--
📄 cpack.1.html	39.49 KB	04/04/2023 07:05:13 PM	rw-r--r--
📄 ctest.1.html	230.72 KB	04/04/2023 07:05:13 PM	rw-r--r--

Editing: cmake-buildsystem.7.html

<!DOCTYPE html>

<title>cmake-buildsystem(7) &mdash; CMake 3.26.3 Documentation</title>

</head><body>

<div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 accesskey="I">index</a></li>
 <li class="right" >
 <a href="cmake-commands.7.html" title="cmake-commands(7)"
 accesskey="N">next</a> |</li>
 <li class="right" >
 <a href="ccmake.1.html" title="ccmake(1)"
 accesskey="P">previous</a> |</li>
 <li>
 <img src="../_static/cmake-logo-16.png" alt=""
 style="vertical-align: middle; margin-top: -2px" />
 </li>
 <li>
 <a href="https://cmake.org/">CMake</a> &#187;
 </li>
 <li>
 <a href="../index.html">3.26.3 Documentation</a> &#187;
 </li>

<li class="nav-item nav-item-this"><a href="">cmake-buildsystem(7)</a></li> 
 </ul>
 </div>

<div class="document">
 <div class="documentwrapper">
 <div class="bodywrapper">
 <div class="body" role="main">
 
 <section id="cmake-buildsystem-7">
<h1><a class="toc-backref" href="#id14" role="doc-backlink">cmake-buildsystem(7)</a><a class="headerlink" href="#cmake-buildsystem-7" title="Permalink to this heading">¶</a></h1>
<nav class="contents" id="contents">
Contents
<ul class="simple">
<li><a class="reference internal" href="#cmake-buildsystem-7" id="id14">cmake-buildsystem(7)</a>
<ul>
<li><a class="reference internal" href="#introduction" id="id15">Introduction</a></li>
<li><a class="reference internal" href="#binary-targets" id="id16">Binary Targets</a>
<ul>
<li><a class="reference internal" href="#binary-executables" id="id17">Binary Executables</a></li>
<li><a class="reference internal" href="#binary-library-types" id="id18">Binary Library Types</a>
<ul>
<li><a class="reference internal" href="#normal-libraries" id="id19">Normal Libraries</a>
<ul>
<li><a class="reference internal" href="#apple-frameworks" id="id20">Apple Frameworks</a></li>
</ul>
</li>
<li><a class="reference internal" href="#object-libraries" id="id21">Object Libraries</a></li>
</ul>
</li>
</ul>
</li>
<li><a class="reference internal" href="#build-specification-and-usage-requirements" id="id22">Build Specification and Usage Requirements</a>
<ul>
<li><a class="reference internal" href="#target-properties" id="id23">Target Properties</a></li>
<li><a class="reference internal" href="#transitive-usage-requirements" id="id24">Transitive Usage Requirements</a></li>
<li><a class="reference internal" href="#compatible-interface-properties" id="id25">Compatible Interface Properties</a></li>
<li><a class="reference internal" href="#property-origin-debugging" id="id26">Property Origin Debugging</a></li>
<li><a class="reference internal" href="#build-specification-with-generator-expressions" id="id27">Build Specification with Generator Expressions</a>
<ul>
<li><a class="reference internal" href="#include-directories-and-usage-requirements" id="id28">Include Directories and Usage Requirements</a></li>
</ul>
</li>
<li><a class="reference internal" href="#link-libraries-and-generator-expressions" id="id29">Link Libraries and Generator Expressions</a></li>
<li><a class="reference internal" href="#output-artifacts" id="id30">Output Artifacts</a>
<ul>
<li><a class="reference internal" href="#runtime-output-artifacts" id="id31">Runtime Output Artifacts</a></li>
<li><a class="reference internal" href="#library-output-artifacts" id="id32">Library Output Artifacts</a></li>
<li><a class="reference internal" href="#archive-output-artifacts" id="id33">Archive Output Artifacts</a></li>
</ul>
</li>
<li><a class="reference internal" href="#directory-scoped-commands" id="id34">Directory-Scoped Commands</a></li>
</ul>
</li>
<li><a class="reference internal" href="#build-configurations" id="id35">Build Configurations</a>
<ul>
<li><a class="reference internal" href="#case-sensitivity" id="id36">Case Sensitivity</a></li>
<li><a class="reference internal" href="#default-and-custom-configurations" id="id37">Default And Custom Configurations</a></li>
</ul>
</li>
<li><a class="reference internal" href="#pseudo-targets" id="id38">Pseudo Targets</a>
<ul>
<li><a class="reference internal" href="#imported-targets" id="id39">Imported Targets</a></li>
<li><a class="reference internal" href="#alias-targets" id="id40">Alias Targets</a></li>
<li><a class="reference internal" href="#interface-libraries" id="id41">Interface Libraries</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</nav>
<section id="introduction">
<h2><a class="toc-backref" href="#id15" role="doc-backlink">Introduction</a><a class="headerlink" href="#introduction" title="Permalink to this heading">¶</a></h2>
A CMake-based buildsystem is organized as a set of high-level logical
targets. Each target corresponds to an executable or library, or
is a custom target containing custom commands. Dependencies between the
targets are expressed in the buildsystem to determine the build order
and the rules for regeneration in response to change.
</section>
<section id="binary-targets">
<h2><a class="toc-backref" href="#id16" role="doc-backlink">Binary Targets</a><a class="headerlink" href="#binary-targets" title="Permalink to this heading">¶</a></h2>
Executables and libraries are defined using the <a class="reference internal" href="../command/add_executable.html#command:add_executable" title="add_executable"><code class="xref cmake cmake-command docutils literal notranslate">add_executable()</code></a>
and <a class="reference internal" href="../command/add_library.html#command:add_library" title="add_library"><code class="xref cmake cmake-command docutils literal notranslate">add_library()</code></a> commands. The resulting binary files have
appropriate <a class="reference internal" href="../prop_tgt/PREFIX.html#prop_tgt:PREFIX" title="PREFIX"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">PREFIX</code></a>, <a class="reference internal" href="../prop_tgt/SUFFIX.html#prop_tgt:SUFFIX" title="SUFFIX"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">SUFFIX</code></a> and extensions for the
platform targeted. Dependencies between binary targets are expressed using
the <a class="reference internal" href="../command/target_link_libraries.html#command:target_link_libraries" title="target_link_libraries"><code class="xref cmake cmake-command docutils literal notranslate">target_link_libraries()</code></a> command:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(archive archive.cpp zip.cpp lzma.cpp)
add_executable(zipapp zipapp.cpp)
target_link_libraries(zipapp archive)
</pre></div>
</div>
<code class="docutils literal notranslate">archive</code> is defined as a <code class="docutils literal notranslate">STATIC</code> library -- an archive containing objects
compiled from <code class="docutils literal notranslate">archive.cpp</code>, <code class="docutils literal notranslate">zip.cpp</code>, and <code class="docutils literal notranslate">lzma.cpp</code>. <code class="docutils literal notranslate">zipapp</code>
is defined as an executable formed by compiling and linking <code class="docutils literal notranslate">zipapp.cpp</code>.
When linking the <code class="docutils literal notranslate">zipapp</code> executable, the <code class="docutils literal notranslate">archive</code> static library is
linked in.
<section id="binary-executables">
<h3><a class="toc-backref" href="#id17" role="doc-backlink">Binary Executables</a><a class="headerlink" href="#binary-executables" title="Permalink to this heading">¶</a></h3>
The <a class="reference internal" href="../command/add_executable.html#command:add_executable" title="add_executable"><code class="xref cmake cmake-command docutils literal notranslate">add_executable()</code></a> command defines an executable target:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_executable(mytool mytool.cpp)
</pre></div>
</div>
Commands such as <a class="reference internal" href="../command/add_custom_command.html#command:add_custom_command" title="add_custom_command"><code class="xref cmake cmake-command docutils literal notranslate">add_custom_command()</code></a>, which generates rules to be
run at build time can transparently use an <a class="reference internal" href="../prop_tgt/TYPE.html#prop_tgt:TYPE" title="TYPE"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">EXECUTABLE</code></a>
target as a <code class="docutils literal notranslate">COMMAND</code> executable. The buildsystem rules will ensure that
the executable is built before attempting to run the command.
</section>
<section id="binary-library-types">
<h3><a class="toc-backref" href="#id18" role="doc-backlink">Binary Library Types</a><a class="headerlink" href="#binary-library-types" title="Permalink to this heading">¶</a></h3>
<section id="normal-libraries">
<h4><a class="toc-backref" href="#id19" role="doc-backlink">Normal Libraries</a><a class="headerlink" href="#normal-libraries" title="Permalink to this heading">¶</a></h4>
By default, the <a class="reference internal" href="../command/add_library.html#command:add_library" title="add_library"><code class="xref cmake cmake-command docutils literal notranslate">add_library()</code></a> command defines a <code class="docutils literal notranslate">STATIC</code> library,
unless a type is specified. A type may be specified when using the command:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(archive SHARED archive.cpp zip.cpp lzma.cpp)
</pre></div>
</div>
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(archive STATIC archive.cpp zip.cpp lzma.cpp)
</pre></div>
</div>
The <a class="reference internal" href="../variable/BUILD_SHARED_LIBS.html#variable:BUILD_SHARED_LIBS" title="BUILD_SHARED_LIBS"><code class="xref cmake cmake-variable docutils literal notranslate">BUILD_SHARED_LIBS</code></a> variable may be enabled to change the
behavior of <a class="reference internal" href="../command/add_library.html#command:add_library" title="add_library"><code class="xref cmake cmake-command docutils literal notranslate">add_library()</code></a> to build shared libraries by default.
In the context of the buildsystem definition as a whole, it is largely
irrelevant whether particular libraries are <code class="docutils literal notranslate">SHARED</code> or <code class="docutils literal notranslate">STATIC</code> --
the commands, dependency specifications and other APIs work similarly
regardless of the library type. The <code class="docutils literal notranslate">MODULE</code> library type is
dissimilar in that it is generally not linked to -- it is not used in
the right-hand-side of the <a class="reference internal" href="../command/target_link_libraries.html#command:target_link_libraries" title="target_link_libraries"><code class="xref cmake cmake-command docutils literal notranslate">target_link_libraries()</code></a> command.
It is a type which is loaded as a plugin using runtime techniques.
If the library does not export any unmanaged symbols (e.g. Windows
resource DLL, C++/CLI DLL), it is required that the library not be a
<code class="docutils literal notranslate">SHARED</code> library because CMake expects <code class="docutils literal notranslate">SHARED</code> libraries to export
at least one symbol.
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(archive MODULE 7z.cpp)
</pre></div>
</div>
<section id="apple-frameworks">
<h5><a class="toc-backref" href="#id20" role="doc-backlink">Apple Frameworks</a><a class="headerlink" href="#apple-frameworks" title="Permalink to this heading">¶</a></h5>
A <code class="docutils literal notranslate">SHARED</code> library may be marked with the <a class="reference internal" href="../prop_tgt/FRAMEWORK.html#prop_tgt:FRAMEWORK" title="FRAMEWORK"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">FRAMEWORK</code></a>
target property to create an macOS or iOS Framework Bundle.
A library with the <code class="docutils literal notranslate">FRAMEWORK</code> target property should also set the
<a class="reference internal" href="../prop_tgt/FRAMEWORK_VERSION.html#prop_tgt:FRAMEWORK_VERSION" title="FRAMEWORK_VERSION"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">FRAMEWORK_VERSION</code></a> target property. This property is typically
set to the value of &quot;A&quot; by macOS conventions.
The <code class="docutils literal notranslate">MACOSX_FRAMEWORK_IDENTIFIER</code> sets the <code class="docutils literal notranslate">CFBundleIdentifier</code> key
and it uniquely identifies the bundle.
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(MyFramework SHARED MyFramework.cpp)
set_target_properties(MyFramework PROPERTIES
 FRAMEWORK TRUE
 FRAMEWORK_VERSION A # Version &quot;A&quot; is macOS convention
 MACOSX_FRAMEWORK_IDENTIFIER org.cmake.MyFramework
)
</pre></div>
</div>
</section>
</section>
<section id="object-libraries">
<h4><a class="toc-backref" href="#id21" role="doc-backlink">Object Libraries</a><a class="headerlink" href="#object-libraries" title="Permalink to this heading">¶</a></h4>
The <code class="docutils literal notranslate">OBJECT</code> library type defines a non-archival collection of object files
resulting from compiling the given source files. The object files collection
may be used as source inputs to other targets by using the syntax
<a class="reference internal" href="cmake-generator-expressions.7.html#genex:TARGET_OBJECTS" title="TARGET_OBJECTS"><code class="xref cmake cmake-genex docutils literal notranslate">$&lt;TARGET_OBJECTS:name&gt;</code></a>. This is a
<a class="reference internal" href="cmake-generator-expressions.7.html#manual:cmake-generator-expressions(7)" title="cmake-generator-expressions(7)"><code class="xref cmake cmake-manual docutils literal notranslate">generator expression</code></a> that can be
used to supply the <code class="docutils literal notranslate">OBJECT</code> library content to other targets:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(archive OBJECT archive.cpp zip.cpp lzma.cpp)

add_library(archiveExtras STATIC $&lt;TARGET_OBJECTS:archive&gt; extras.cpp)

add_executable(test_exe $&lt;TARGET_OBJECTS:archive&gt; test.cpp)
</pre></div>
</div>
The link (or archiving) step of those other targets will use the object
files collection in addition to those from their own sources.
Alternatively, object libraries may be linked into other targets:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(archive OBJECT archive.cpp zip.cpp lzma.cpp)

add_library(archiveExtras STATIC extras.cpp)
target_link_libraries(archiveExtras PUBLIC archive)

add_executable(test_exe test.cpp)
target_link_libraries(test_exe archive)
</pre></div>
</div>
The link (or archiving) step of those other targets will use the object
files from <code class="docutils literal notranslate">OBJECT</code> libraries that are directly linked. Additionally,
usage requirements of the <code class="docutils literal notranslate">OBJECT</code> libraries will be honored when compiling
sources in those other targets. Furthermore, those usage requirements
will propagate transitively to dependents of those other targets.
Object libraries may not be used as the <code class="docutils literal notranslate">TARGET</code> in a use of the
<a class="reference internal" href="../command/add_custom_command.html#command:add_custom_command" title="add_custom_command"><code class="xref cmake cmake-command docutils literal notranslate">add_custom_command(TARGET)</code></a> command signature. However,
the list of objects can be used by <a class="reference internal" href="../command/add_custom_command.html#command:add_custom_command" title="add_custom_command"><code class="xref cmake cmake-command docutils literal notranslate">add_custom_command(OUTPUT)</code></a>
or <a class="reference internal" href="../command/file.html#command:file" title="file"><code class="xref cmake cmake-command docutils literal notranslate">file(GENERATE)</code></a> by using <code class="docutils literal notranslate">$&lt;TARGET_OBJECTS:objlib&gt;</code>.
</section>
</section>
</section>
<section id="build-specification-and-usage-requirements">
<h2><a class="toc-backref" href="#id22" role="doc-backlink">Build Specification and Usage Requirements</a><a class="headerlink" href="#build-specification-and-usage-requirements" title="Permalink to this heading">¶</a></h2>
The <a class="reference internal" href="../command/target_include_directories.html#command:target_include_directories" title="target_include_directories"><code class="xref cmake cmake-command docutils literal notranslate">target_include_directories()</code></a>, <a class="reference internal" href="../command/target_compile_definitions.html#command:target_compile_definitions" title="target_compile_definitions"><code class="xref cmake cmake-command docutils literal notranslate">target_compile_definitions()</code></a>
and <a class="reference internal" href="../command/target_compile_options.html#command:target_compile_options" title="target_compile_options"><code class="xref cmake cmake-command docutils literal notranslate">target_compile_options()</code></a> commands specify the build specifications
and the usage requirements of binary targets. The commands populate the
<a class="reference internal" href="../prop_tgt/INCLUDE_DIRECTORIES.html#prop_tgt:INCLUDE_DIRECTORIES" title="INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INCLUDE_DIRECTORIES</code></a>, <a class="reference internal" href="../prop_tgt/COMPILE_DEFINITIONS.html#prop_tgt:COMPILE_DEFINITIONS" title="COMPILE_DEFINITIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPILE_DEFINITIONS</code></a> and
<a class="reference internal" href="../prop_tgt/COMPILE_OPTIONS.html#prop_tgt:COMPILE_OPTIONS" title="COMPILE_OPTIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPILE_OPTIONS</code></a> target properties respectively, and/or the
<a class="reference internal" href="../prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html#prop_tgt:INTERFACE_INCLUDE_DIRECTORIES" title="INTERFACE_INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_INCLUDE_DIRECTORIES</code></a>, <a class="reference internal" href="../prop_tgt/INTERFACE_COMPILE_DEFINITIONS.html#prop_tgt:INTERFACE_COMPILE_DEFINITIONS" title="INTERFACE_COMPILE_DEFINITIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_COMPILE_DEFINITIONS</code></a>
and <a class="reference internal" href="../prop_tgt/INTERFACE_COMPILE_OPTIONS.html#prop_tgt:INTERFACE_COMPILE_OPTIONS" title="INTERFACE_COMPILE_OPTIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_COMPILE_OPTIONS</code></a> target properties.
Each of the commands has a <code class="docutils literal notranslate">PRIVATE</code>, <code class="docutils literal notranslate">PUBLIC</code> and <code class="docutils literal notranslate">INTERFACE</code> mode. The
<code class="docutils literal notranslate">PRIVATE</code> mode populates only the non-<code class="docutils literal notranslate">INTERFACE_</code> variant of the target
property and the <code class="docutils literal notranslate">INTERFACE</code> mode populates only the <code class="docutils literal notranslate">INTERFACE_</code> variants.
The <code class="docutils literal notranslate">PUBLIC</code> mode populates both variants of the respective target property.
Each command may be invoked with multiple uses of each keyword:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>target_compile_definitions(archive
 PRIVATE BUILDING_WITH_LZMA
 INTERFACE USING_ARCHIVE_LIB
)
</pre></div>
</div>
Note that usage requirements are not designed as a way to make downstreams
use particular <a class="reference internal" href="../prop_tgt/COMPILE_OPTIONS.html#prop_tgt:COMPILE_OPTIONS" title="COMPILE_OPTIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPILE_OPTIONS</code></a> or
<a class="reference internal" href="../prop_tgt/COMPILE_DEFINITIONS.html#prop_tgt:COMPILE_DEFINITIONS" title="COMPILE_DEFINITIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPILE_DEFINITIONS</code></a> etc for convenience only. The contents of
the properties must be requirements, not merely recommendations or
convenience.
See the <a class="reference internal" href="cmake-packages.7.html#creating-relocatable-packages">Creating Relocatable Packages</a> section of the
<a class="reference internal" href="cmake-packages.7.html#manual:cmake-packages(7)" title="cmake-packages(7)"><code class="xref cmake cmake-manual docutils literal notranslate">cmake-packages(7)</code></a> manual for discussion of additional care
that must be taken when specifying usage requirements while creating
packages for redistribution.
<section id="target-properties">
<h3><a class="toc-backref" href="#id23" role="doc-backlink">Target Properties</a><a class="headerlink" href="#target-properties" title="Permalink to this heading">¶</a></h3>
The contents of the <a class="reference internal" href="../prop_tgt/INCLUDE_DIRECTORIES.html#prop_tgt:INCLUDE_DIRECTORIES" title="INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INCLUDE_DIRECTORIES</code></a>,
<a class="reference internal" href="../prop_tgt/COMPILE_DEFINITIONS.html#prop_tgt:COMPILE_DEFINITIONS" title="COMPILE_DEFINITIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPILE_DEFINITIONS</code></a> and <a class="reference internal" href="../prop_tgt/COMPILE_OPTIONS.html#prop_tgt:COMPILE_OPTIONS" title="COMPILE_OPTIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPILE_OPTIONS</code></a> target
properties are used appropriately when compiling the source files of a
binary target.
Entries in the <a class="reference internal" href="../prop_tgt/INCLUDE_DIRECTORIES.html#prop_tgt:INCLUDE_DIRECTORIES" title="INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INCLUDE_DIRECTORIES</code></a> are added to the compile line
with <code class="docutils literal notranslate">-I</code> or <code class="docutils literal notranslate">-isystem</code> prefixes and in the order of appearance in the
property value.
Entries in the <a class="reference internal" href="../prop_tgt/COMPILE_DEFINITIONS.html#prop_tgt:COMPILE_DEFINITIONS" title="COMPILE_DEFINITIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPILE_DEFINITIONS</code></a> are prefixed with <code class="docutils literal notranslate">-D</code> or
<code class="docutils literal notranslate">/D</code> and added to the compile line in an unspecified order. The
<a class="reference internal" href="../prop_tgt/DEFINE_SYMBOL.html#prop_tgt:DEFINE_SYMBOL" title="DEFINE_SYMBOL"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">DEFINE_SYMBOL</code></a> target property is also added as a compile
definition as a special convenience case for <code class="docutils literal notranslate">SHARED</code> and <code class="docutils literal notranslate">MODULE</code>
library targets.
Entries in the <a class="reference internal" href="../prop_tgt/COMPILE_OPTIONS.html#prop_tgt:COMPILE_OPTIONS" title="COMPILE_OPTIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPILE_OPTIONS</code></a> are escaped for the shell and added
in the order of appearance in the property value. Several compile options have
special separate handling, such as <a class="reference internal" href="../prop_tgt/POSITION_INDEPENDENT_CODE.html#prop_tgt:POSITION_INDEPENDENT_CODE" title="POSITION_INDEPENDENT_CODE"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">POSITION_INDEPENDENT_CODE</code></a>.
The contents of the <a class="reference internal" href="../prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html#prop_tgt:INTERFACE_INCLUDE_DIRECTORIES" title="INTERFACE_INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_INCLUDE_DIRECTORIES</code></a>,
<a class="reference internal" href="../prop_tgt/INTERFACE_COMPILE_DEFINITIONS.html#prop_tgt:INTERFACE_COMPILE_DEFINITIONS" title="INTERFACE_COMPILE_DEFINITIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_COMPILE_DEFINITIONS</code></a> and
<a class="reference internal" href="../prop_tgt/INTERFACE_COMPILE_OPTIONS.html#prop_tgt:INTERFACE_COMPILE_OPTIONS" title="INTERFACE_COMPILE_OPTIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_COMPILE_OPTIONS</code></a> target properties are
Usage Requirements -- they specify content which consumers
must use to correctly compile and link with the target they appear on.
For any binary target, the contents of each <code class="docutils literal notranslate">INTERFACE_</code> property on
each target specified in a <a class="reference internal" href="../command/target_link_libraries.html#command:target_link_libraries" title="target_link_libraries"><code class="xref cmake cmake-command docutils literal notranslate">target_link_libraries()</code></a> command is
consumed:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>set(srcs archive.cpp zip.cpp)
if (LZMA_FOUND)
 list(APPEND srcs lzma.cpp)
endif()
add_library(archive SHARED ${srcs})
if (LZMA_FOUND)
 # The archive library sources are compiled with -DBUILDING_WITH_LZMA
 target_compile_definitions(archive PRIVATE BUILDING_WITH_LZMA)
endif()
target_compile_definitions(archive INTERFACE USING_ARCHIVE_LIB)

add_executable(consumer)
# Link consumer to archive and consume its usage requirements. The consumer
# executable sources are compiled with -DUSING_ARCHIVE_LIB.
target_link_libraries(consumer archive)
</pre></div>
</div>
Because it is common to require that the source directory and corresponding
build directory are added to the <a class="reference internal" href="../prop_tgt/INCLUDE_DIRECTORIES.html#prop_tgt:INCLUDE_DIRECTORIES" title="INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INCLUDE_DIRECTORIES</code></a>, the
<a class="reference internal" href="../variable/CMAKE_INCLUDE_CURRENT_DIR.html#variable:CMAKE_INCLUDE_CURRENT_DIR" title="CMAKE_INCLUDE_CURRENT_DIR"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_INCLUDE_CURRENT_DIR</code></a> variable can be enabled to conveniently
add the corresponding directories to the <a class="reference internal" href="../prop_tgt/INCLUDE_DIRECTORIES.html#prop_tgt:INCLUDE_DIRECTORIES" title="INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INCLUDE_DIRECTORIES</code></a> of
all targets. The variable <a class="reference internal" href="../variable/CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE.html#variable:CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE" title="CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE</code></a>
can be enabled to add the corresponding directories to the
<a class="reference internal" href="../prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html#prop_tgt:INTERFACE_INCLUDE_DIRECTORIES" title="INTERFACE_INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_INCLUDE_DIRECTORIES</code></a> of all targets. This makes use of
targets in multiple different directories convenient through use of the
<a class="reference internal" href="../command/target_link_libraries.html#command:target_link_libraries" title="target_link_libraries"><code class="xref cmake cmake-command docutils literal notranslate">target_link_libraries()</code></a> command.
</section>
<section id="transitive-usage-requirements">
<h3><a class="toc-backref" href="#id24" role="doc-backlink">Transitive Usage Requirements</a><a class="headerlink" href="#transitive-usage-requirements" title="Permalink to this heading">¶</a></h3>
The usage requirements of a target can transitively propagate to the dependents.
The <a class="reference internal" href="../command/target_link_libraries.html#command:target_link_libraries" title="target_link_libraries"><code class="xref cmake cmake-command docutils literal notranslate">target_link_libraries()</code></a> command has <code class="docutils literal notranslate">PRIVATE</code>,
<code class="docutils literal notranslate">INTERFACE</code> and <code class="docutils literal notranslate">PUBLIC</code> keywords to control the propagation.
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(archive archive.cpp)
target_compile_definitions(archive INTERFACE USING_ARCHIVE_LIB)

add_library(serialization serialization.cpp)
target_compile_definitions(serialization INTERFACE USING_SERIALIZATION_LIB)

add_library(archiveExtras extras.cpp)
target_link_libraries(archiveExtras PUBLIC archive)
target_link_libraries(archiveExtras PRIVATE serialization)
# archiveExtras is compiled with -DUSING_ARCHIVE_LIB
# and -DUSING_SERIALIZATION_LIB

add_executable(consumer consumer.cpp)
# consumer is compiled with -DUSING_ARCHIVE_LIB
target_link_libraries(consumer archiveExtras)
</pre></div>
</div>
Because the <code class="docutils literal notranslate">archive</code> is a <code class="docutils literal notranslate">PUBLIC</code> dependency of <code class="docutils literal notranslate">archiveExtras</code>, the
usage requirements of it are propagated to <code class="docutils literal notranslate">consumer</code> too.
Because
<code class="docutils literal notranslate">serialization</code> is a <code class="docutils literal notranslate">PRIVATE</code> dependency of <code class="docutils literal notranslate">archiveExtras</code>, the usage
requirements of it are not propagated to <code class="docutils literal notranslate">consumer</code>.
Generally, a dependency should be specified in a use of
<a class="reference internal" href="../command/target_link_libraries.html#command:target_link_libraries" title="target_link_libraries"><code class="xref cmake cmake-command docutils literal notranslate">target_link_libraries()</code></a> with the <code class="docutils literal notranslate">PRIVATE</code> keyword if it is used by
only the implementation of a library, and not in the header files. If a
dependency is additionally used in the header files of a library (e.g. for
class inheritance), then it should be specified as a <code class="docutils literal notranslate">PUBLIC</code> dependency.
A dependency which is not used by the implementation of a library, but only by
its headers should be specified as an <code class="docutils literal notranslate">INTERFACE</code> dependency. The
<a class="reference internal" href="../command/target_link_libraries.html#command:target_link_libraries" title="target_link_libraries"><code class="xref cmake cmake-command docutils literal notranslate">target_link_libraries()</code></a> command may be invoked with multiple uses of
each keyword:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>target_link_libraries(archiveExtras
 PUBLIC archive
 PRIVATE serialization
)
</pre></div>
</div>
Usage requirements are propagated by reading the <code class="docutils literal notranslate">INTERFACE_</code> variants
of target properties from dependencies and appending the values to the
non-<code class="docutils literal notranslate">INTERFACE_</code> variants of the operand. For example, the
<a class="reference internal" href="../prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html#prop_tgt:INTERFACE_INCLUDE_DIRECTORIES" title="INTERFACE_INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_INCLUDE_DIRECTORIES</code></a> of dependencies is read and
appended to the <a class="reference internal" href="../prop_tgt/INCLUDE_DIRECTORIES.html#prop_tgt:INCLUDE_DIRECTORIES" title="INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INCLUDE_DIRECTORIES</code></a> of the operand. In cases
where order is relevant and maintained, and the order resulting from the
<a class="reference internal" href="../command/target_link_libraries.html#command:target_link_libraries" title="target_link_libraries"><code class="xref cmake cmake-command docutils literal notranslate">target_link_libraries()</code></a> calls does not allow correct compilation,
use of an appropriate command to set the property directly may update the
order.
For example, if the linked libraries for a target must be specified
in the order <code class="docutils literal notranslate">lib1</code> <code class="docutils literal notranslate">lib2</code> <code class="docutils literal notranslate">lib3</code> , but the include directories must
be specified in the order <code class="docutils literal notranslate">lib3</code> <code class="docutils literal notranslate">lib1</code> <code class="docutils literal notranslate">lib2</code>:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>target_link_libraries(myExe lib1 lib2 lib3)
target_include_directories(myExe
 PRIVATE $&lt;TARGET_PROPERTY:lib3,INTERFACE_INCLUDE_DIRECTORIES&gt;)
</pre></div>
</div>
Note that care must be taken when specifying usage requirements for targets
which will be exported for installation using the <a class="reference internal" href="../command/install.html#command:install" title="install"><code class="xref cmake cmake-command docutils literal notranslate">install(EXPORT)</code></a>
command. See <a class="reference internal" href="cmake-packages.7.html#creating-packages">Creating Packages</a> for more.
</section>
<section id="compatible-interface-properties">
<h3><a class="toc-backref" href="#id25" role="doc-backlink">Compatible Interface Properties</a><a class="headerlink" href="#compatible-interface-properties" title="Permalink to this heading">¶</a></h3>
Some target properties are required to be compatible between a target and
the interface of each dependency. For example, the
<a class="reference internal" href="../prop_tgt/POSITION_INDEPENDENT_CODE.html#prop_tgt:POSITION_INDEPENDENT_CODE" title="POSITION_INDEPENDENT_CODE"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">POSITION_INDEPENDENT_CODE</code></a> target property may specify a
boolean value of whether a target should be compiled as
position-independent-code, which has platform-specific consequences.
A target may also specify the usage requirement
<a class="reference internal" href="../prop_tgt/INTERFACE_POSITION_INDEPENDENT_CODE.html#prop_tgt:INTERFACE_POSITION_INDEPENDENT_CODE" title="INTERFACE_POSITION_INDEPENDENT_CODE"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_POSITION_INDEPENDENT_CODE</code></a> to communicate that
consumers must be compiled as position-independent-code.
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_executable(exe1 exe1.cpp)
set_property(TARGET exe1 PROPERTY POSITION_INDEPENDENT_CODE ON)

add_library(lib1 SHARED lib1.cpp)
set_property(TARGET lib1 PROPERTY INTERFACE_POSITION_INDEPENDENT_CODE ON)

add_executable(exe2 exe2.cpp)
target_link_libraries(exe2 lib1)
</pre></div>
</div>
Here, both <code class="docutils literal notranslate">exe1</code> and <code class="docutils literal notranslate">exe2</code> will be compiled as position-independent-code.
<code class="docutils literal notranslate">lib1</code> will also be compiled as position-independent-code because that is the
default setting for <code class="docutils literal notranslate">SHARED</code> libraries. If dependencies have conflicting,
non-compatible requirements <a class="reference internal" href="cmake.1.html#manual:cmake(1)" title="cmake(1)"><code class="xref cmake cmake-manual docutils literal notranslate">cmake(1)</code></a> issues a diagnostic:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(lib1 SHARED lib1.cpp)
set_property(TARGET lib1 PROPERTY INTERFACE_POSITION_INDEPENDENT_CODE ON)

add_library(lib2 SHARED lib2.cpp)
set_property(TARGET lib2 PROPERTY INTERFACE_POSITION_INDEPENDENT_CODE OFF)

add_executable(exe2 exe2.cpp)
target_link_libraries(exe2 lib1 lib2)
</pre></div>
</div>
The <code class="docutils literal notranslate">lib1</code> requirement <code class="docutils literal notranslate">INTERFACE_POSITION_INDEPENDENT_CODE</code> is not
&quot;compatible&quot; with the <a class="reference internal" href="../prop_tgt/POSITION_INDEPENDENT_CODE.html#prop_tgt:POSITION_INDEPENDENT_CODE" title="POSITION_INDEPENDENT_CODE"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">POSITION_INDEPENDENT_CODE</code></a> property of
the <code class="docutils literal notranslate">exe1</code> target. The library requires that consumers are built as
position-independent-code, while the executable specifies to not built as
position-independent-code, so a diagnostic is issued.
The <code class="docutils literal notranslate">lib1</code> and <code class="docutils literal notranslate">lib2</code> requirements are not &quot;compatible&quot;. One of them
requires that consumers are built as position-independent-code, while
the other requires that consumers are not built as position-independent-code.
Because <code class="docutils literal notranslate">exe2</code> links to both and they are in conflict, a CMake error message
is issued:
<div class="highlight-none notranslate"><div class="highlight"><pre>CMake Error: The INTERFACE_POSITION_INDEPENDENT_CODE property of &quot;lib2&quot; does
not agree with the value of POSITION_INDEPENDENT_CODE already determined
for &quot;exe2&quot;.
</pre></div>
</div>
To be &quot;compatible&quot;, the <a class="reference internal" href="../prop_tgt/POSITION_INDEPENDENT_CODE.html#prop_tgt:POSITION_INDEPENDENT_CODE" title="POSITION_INDEPENDENT_CODE"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">POSITION_INDEPENDENT_CODE</code></a> property,
if set must be either the same, in a boolean sense, as the
<a class="reference internal" href="../prop_tgt/INTERFACE_POSITION_INDEPENDENT_CODE.html#prop_tgt:INTERFACE_POSITION_INDEPENDENT_CODE" title="INTERFACE_POSITION_INDEPENDENT_CODE"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_POSITION_INDEPENDENT_CODE</code></a> property of all transitively
specified dependencies on which that property is set.
This property of &quot;compatible interface requirement&quot; may be extended to other
properties by specifying the property in the content of the
<a class="reference internal" href="../prop_tgt/COMPATIBLE_INTERFACE_BOOL.html#prop_tgt:COMPATIBLE_INTERFACE_BOOL" title="COMPATIBLE_INTERFACE_BOOL"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPATIBLE_INTERFACE_BOOL</code></a> target property. Each specified property
must be compatible between the consuming target and the corresponding property
with an <code class="docutils literal notranslate">INTERFACE_</code> prefix from each dependency:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(lib1Version2 SHARED lib1_v2.cpp)
set_property(TARGET lib1Version2 PROPERTY INTERFACE_CUSTOM_PROP ON)
set_property(TARGET lib1Version2 APPEND PROPERTY
 COMPATIBLE_INTERFACE_BOOL CUSTOM_PROP
)

add_library(lib1Version3 SHARED lib1_v3.cpp)
set_property(TARGET lib1Version3 PROPERTY INTERFACE_CUSTOM_PROP OFF)

add_executable(exe2 exe2.cpp)
target_link_libraries(exe2 lib1Version2 lib1Version3) # Diagnostic
</pre></div>
</div>
Non-boolean properties may also participate in &quot;compatible interface&quot;
computations. Properties specified in the
<a class="reference internal" href="../prop_tgt/COMPATIBLE_INTERFACE_STRING.html#prop_tgt:COMPATIBLE_INTERFACE_STRING" title="COMPATIBLE_INTERFACE_STRING"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPATIBLE_INTERFACE_STRING</code></a>
property must be either unspecified or compare to the same string among
all transitively specified dependencies. This can be useful to ensure
that multiple incompatible versions of a library are not linked together
through transitive requirements of a target:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(lib1Version2 SHARED lib1_v2.cpp)
set_property(TARGET lib1Version2 PROPERTY INTERFACE_LIB_VERSION 2)
set_property(TARGET lib1Version2 APPEND PROPERTY
 COMPATIBLE_INTERFACE_STRING LIB_VERSION
)

add_library(lib1Version3 SHARED lib1_v3.cpp)
set_property(TARGET lib1Version3 PROPERTY INTERFACE_LIB_VERSION 3)

add_executable(exe2 exe2.cpp)
target_link_libraries(exe2 lib1Version2 lib1Version3) # Diagnostic
</pre></div>
</div>
The <a class="reference internal" href="../prop_tgt/COMPATIBLE_INTERFACE_NUMBER_MAX.html#prop_tgt:COMPATIBLE_INTERFACE_NUMBER_MAX" title="COMPATIBLE_INTERFACE_NUMBER_MAX"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPATIBLE_INTERFACE_NUMBER_MAX</code></a> target property specifies
that content will be evaluated numerically and the maximum number among all
specified will be calculated:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(lib1Version2 SHARED lib1_v2.cpp)
set_property(TARGET lib1Version2 PROPERTY INTERFACE_CONTAINER_SIZE_REQUIRED 200)
set_property(TARGET lib1Version2 APPEND PROPERTY
 COMPATIBLE_INTERFACE_NUMBER_MAX CONTAINER_SIZE_REQUIRED
)

add_library(lib1Version3 SHARED lib1_v3.cpp)
set_property(TARGET lib1Version3 PROPERTY INTERFACE_CONTAINER_SIZE_REQUIRED 1000)

add_executable(exe1 exe1.cpp)
# CONTAINER_SIZE_REQUIRED will be &quot;200&quot;
target_link_libraries(exe1 lib1Version2)

add_executable(exe2 exe2.cpp)
# CONTAINER_SIZE_REQUIRED will be &quot;1000&quot;
target_link_libraries(exe2 lib1Version2 lib1Version3)
</pre></div>
</div>
Similarly, the <a class="reference internal" href="../prop_tgt/COMPATIBLE_INTERFACE_NUMBER_MIN.html#prop_tgt:COMPATIBLE_INTERFACE_NUMBER_MIN" title="COMPATIBLE_INTERFACE_NUMBER_MIN"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPATIBLE_INTERFACE_NUMBER_MIN</code></a> may be used to
calculate the numeric minimum value for a property from dependencies.
Each calculated &quot;compatible&quot; property value may be read in the consumer at
generate-time using generator expressions.
Note that for each dependee, the set of properties specified in each
compatible interface property must not intersect with the set specified in
any of the other properties.
</section>
<section id="property-origin-debugging">
<h3><a class="toc-backref" href="#id26" role="doc-backlink">Property Origin Debugging</a><a class="headerlink" href="#property-origin-debugging" title="Permalink to this heading">¶</a></h3>
Because build specifications can be determined by dependencies, the lack of
locality of code which creates a target and code which is responsible for
setting build specifications may make the code more difficult to reason about.
<a class="reference internal" href="cmake.1.html#manual:cmake(1)" title="cmake(1)"><code class="xref cmake cmake-manual docutils literal notranslate">cmake(1)</code></a> provides a debugging facility to print the origin of the
contents of properties which may be determined by dependencies. The properties
which can be debugged are listed in the
<a class="reference internal" href="../variable/CMAKE_DEBUG_TARGET_PROPERTIES.html#variable:CMAKE_DEBUG_TARGET_PROPERTIES" title="CMAKE_DEBUG_TARGET_PROPERTIES"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_DEBUG_TARGET_PROPERTIES</code></a> variable documentation:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>set(CMAKE_DEBUG_TARGET_PROPERTIES
 INCLUDE_DIRECTORIES
 COMPILE_DEFINITIONS
 POSITION_INDEPENDENT_CODE
 CONTAINER_SIZE_REQUIRED
 LIB_VERSION
)
add_executable(exe1 exe1.cpp)
</pre></div>
</div>
In the case of properties listed in <a class="reference internal" href="../prop_tgt/COMPATIBLE_INTERFACE_BOOL.html#prop_tgt:COMPATIBLE_INTERFACE_BOOL" title="COMPATIBLE_INTERFACE_BOOL"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPATIBLE_INTERFACE_BOOL</code></a> or
<a class="reference internal" href="../prop_tgt/COMPATIBLE_INTERFACE_STRING.html#prop_tgt:COMPATIBLE_INTERFACE_STRING" title="COMPATIBLE_INTERFACE_STRING"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPATIBLE_INTERFACE_STRING</code></a>, the debug output shows which target
was responsible for setting the property, and which other dependencies also
defined the property. In the case of
<a class="reference internal" href="../prop_tgt/COMPATIBLE_INTERFACE_NUMBER_MAX.html#prop_tgt:COMPATIBLE_INTERFACE_NUMBER_MAX" title="COMPATIBLE_INTERFACE_NUMBER_MAX"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPATIBLE_INTERFACE_NUMBER_MAX</code></a> and
<a class="reference internal" href="../prop_tgt/COMPATIBLE_INTERFACE_NUMBER_MIN.html#prop_tgt:COMPATIBLE_INTERFACE_NUMBER_MIN" title="COMPATIBLE_INTERFACE_NUMBER_MIN"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">COMPATIBLE_INTERFACE_NUMBER_MIN</code></a>, the debug output shows the
value of the property from each dependency, and whether the value determines
the new extreme.
</section>
<section id="build-specification-with-generator-expressions">
<h3><a class="toc-backref" href="#id27" role="doc-backlink">Build Specification with Generator Expressions</a><a class="headerlink" href="#build-specification-with-generator-expressions" title="Permalink to this heading">¶</a></h3>
Build specifications may use
<a class="reference internal" href="cmake-generator-expressions.7.html#manual:cmake-generator-expressions(7)" title="cmake-generator-expressions(7)"><code class="xref cmake cmake-manual docutils literal notranslate">generator expressions</code></a> containing
content which may be conditional or known only at generate-time. For example,
the calculated &quot;compatible&quot; value of a property may be read with the
<code class="docutils literal notranslate">TARGET_PROPERTY</code> expression:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(lib1Version2 SHARED lib1_v2.cpp)
set_property(TARGET lib1Version2 PROPERTY
 INTERFACE_CONTAINER_SIZE_REQUIRED 200)
set_property(TARGET lib1Version2 APPEND PROPERTY
 COMPATIBLE_INTERFACE_NUMBER_MAX CONTAINER_SIZE_REQUIRED
)

cmake_policy(SET CMP0041 NEW)

add_library(shared_lib shared_lib.cpp)
target_link_libraries(shared_lib lib1)
</pre></div>
</div>
The <code class="docutils literal notranslate">exe1</code> executable will be compiled with <code class="docutils literal notranslate">-DLIB1_WITH_EXE</code>, while the
<code class="docutils literal notranslate">shared_lib</code> shared library will be compiled with <code class="docutils literal notranslate">-DLIB1_WITH_SHARED_LIB</code>
and <code class="docutils literal notranslate">-DCONSUMER_CMP0041_NEW</code>, because policy <a class="reference internal" href="../policy/CMP0041.html#policy:CMP0041" title="CMP0041"><code class="xref cmake cmake-policy docutils literal notranslate">CMP0041</code></a> is
<code class="docutils literal notranslate">NEW</code> at the point where the <code class="docutils literal notranslate">shared_lib</code> target is created.
The <code class="docutils literal notranslate">BUILD_INTERFACE</code> expression wraps requirements which are only used when
consumed from a target in the same buildsystem, or when consumed from a target
exported to the build directory using the <a class="reference internal" href="../command/export.html#command:export" title="export"><code class="xref cmake cmake-command docutils literal notranslate">export()</code></a> command. The
<code class="docutils literal notranslate">INSTALL_INTERFACE</code> expression wraps requirements which are only used when
consumed from a target which has been installed and exported with the
<a class="reference internal" href="../command/install.html#command:install" title="install"><code class="xref cmake cmake-command docutils literal notranslate">install(EXPORT)</code></a> command:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(ClimbingStats climbingstats.cpp)
target_compile_definitions(ClimbingStats INTERFACE
 $&lt;BUILD_INTERFACE:ClimbingStats_FROM_BUILD_LOCATION&gt;
 $&lt;INSTALL_INTERFACE:ClimbingStats_FROM_INSTALLED_LOCATION&gt;
)
install(TARGETS ClimbingStats EXPORT libExport ${InstallArgs})
install(EXPORT libExport NAMESPACE Upstream::
 DESTINATION lib/cmake/ClimbingStats)
export(EXPORT libExport NAMESPACE Upstream::)

add_executable(Downstream main.cpp)
target_link_libraries(Downstream Upstream::ClimbingStats)
</pre></div>
</div>
Depending on whether the <code class="docutils literal notranslate">ClimbingStats</code> package was used from the build
location or the install location, the <code class="docutils literal notranslate">Downstream</code> target would be compiled
with either <code class="docutils literal notranslate">-DClimbingStats_FROM_BUILD_LOCATION</code> or
<code class="docutils literal notranslate">-DClimbingStats_FROM_INSTALL_LOCATION</code>. For more about packages and
exporting see the <a class="reference internal" href="cmake-packages.7.html#manual:cmake-packages(7)" title="cmake-packages(7)"><code class="xref cmake cmake-manual docutils literal notranslate">cmake-packages(7)</code></a> manual.
<section id="include-directories-and-usage-requirements">
<h4><a class="toc-backref" href="#id28" role="doc-backlink">Include Directories and Usage Requirements</a><a class="headerlink" href="#include-directories-and-usage-requirements" title="Permalink to this heading">¶</a></h4>
Include directories require some special consideration when specified as usage
requirements and when used with generator expressions. The
<a class="reference internal" href="../command/target_include_directories.html#command:target_include_directories" title="target_include_directories"><code class="xref cmake cmake-command docutils literal notranslate">target_include_directories()</code></a> command accepts both relative and
absolute include directories:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(lib1 lib1.cpp)
target_include_directories(lib1 PRIVATE
 /absolute/path
 relative/path
)
</pre></div>
</div>
Relative paths are interpreted relative to the source directory where the
command appears. Relative paths are not allowed in the
<a class="reference internal" href="../prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html#prop_tgt:INTERFACE_INCLUDE_DIRECTORIES" title="INTERFACE_INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_INCLUDE_DIRECTORIES</code></a> of <a class="reference internal" href="../prop_tgt/IMPORTED.html#prop_tgt:IMPORTED" title="IMPORTED"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">IMPORTED</code></a> targets.
In cases where a non-trivial generator expression is used, the
<code class="docutils literal notranslate">INSTALL_PREFIX</code> expression may be used within the argument of an
<code class="docutils literal notranslate">INSTALL_INTERFACE</code> expression. It is a replacement marker which
expands to the installation prefix when imported by a consuming project.
Include directories usage requirements commonly differ between the build-tree
and the install-tree. The <code class="docutils literal notranslate">BUILD_INTERFACE</code> and <code class="docutils literal notranslate">INSTALL_INTERFACE</code>
generator expressions can be used to describe separate usage requirements
based on the usage location. Relative paths are allowed within the
<code class="docutils literal notranslate">INSTALL_INTERFACE</code> expression and are interpreted relative to the
installation prefix. For example:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(ClimbingStats climbingstats.cpp)
target_include_directories(ClimbingStats INTERFACE
 $&lt;BUILD_INTERFACE:${CMAKE_CURRENT_BINARY_DIR}/generated&gt;
 $&lt;INSTALL_INTERFACE:/absolute/path&gt;
 $&lt;INSTALL_INTERFACE:relative/path&gt;
 $&lt;INSTALL_INTERFACE:$&lt;INSTALL_PREFIX&gt;/$&lt;CONFIG&gt;/generated&gt;
)
</pre></div>
</div>
Two convenience APIs are provided relating to include directories usage
requirements. The <a class="reference internal" href="../variable/CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE.html#variable:CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE" title="CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE</code></a> variable
may be enabled, with an equivalent effect to:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>set_property(TARGET tgt APPEND PROPERTY INTERFACE_INCLUDE_DIRECTORIES
 $&lt;BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR};${CMAKE_CURRENT_BINARY_DIR}&gt;
)
</pre></div>
</div>
for each target affected. The convenience for installed targets is
an <code class="docutils literal notranslate">INCLUDES DESTINATION</code> component with the <a class="reference internal" href="../command/install.html#command:install" title="install"><code class="xref cmake cmake-command docutils literal notranslate">install(TARGETS)</code></a>
command:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>install(TARGETS foo bar bat EXPORT tgts ${dest_args}
 INCLUDES DESTINATION include
)
install(EXPORT tgts ${other_args})
install(FILES ${headers} DESTINATION include)
</pre></div>
</div>
This is equivalent to appending <code class="docutils literal notranslate">${CMAKE_INSTALL_PREFIX}/include</code> to the
<a class="reference internal" href="../prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html#prop_tgt:INTERFACE_INCLUDE_DIRECTORIES" title="INTERFACE_INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_INCLUDE_DIRECTORIES</code></a> of each of the installed
<a class="reference internal" href="../prop_tgt/IMPORTED.html#prop_tgt:IMPORTED" title="IMPORTED"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">IMPORTED</code></a> targets when generated by <a class="reference internal" href="../command/install.html#command:install" title="install"><code class="xref cmake cmake-command docutils literal notranslate">install(EXPORT)</code></a>.
When the <a class="reference internal" href="../prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html#prop_tgt:INTERFACE_INCLUDE_DIRECTORIES" title="INTERFACE_INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_INCLUDE_DIRECTORIES</code></a> of an
<a class="reference internal" href="#imported-targets">imported target</a> is consumed, the entries in the
property may be treated as system include directories. The effects of that
are toolchain-dependent, but one common effect is to omit compiler warnings
for headers found in those directories. The <a class="reference internal" href="../prop_tgt/SYSTEM.html#prop_tgt:SYSTEM" title="SYSTEM"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">SYSTEM</code></a> property of
the installed target determines this behavior (see the
<a class="reference internal" href="../prop_tgt/EXPORT_NO_SYSTEM.html#prop_tgt:EXPORT_NO_SYSTEM" title="EXPORT_NO_SYSTEM"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">EXPORT_NO_SYSTEM</code></a> property for how to modify the installed value
for a target). It is also possible to change how consumers interpret the
system behavior of consumed imported targets by setting the
<a class="reference internal" href="../prop_tgt/NO_SYSTEM_FROM_IMPORTED.html#prop_tgt:NO_SYSTEM_FROM_IMPORTED" title="NO_SYSTEM_FROM_IMPORTED"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">NO_SYSTEM_FROM_IMPORTED</code></a> target property on the consumer.
If a binary target is linked transitively to a macOS <a class="reference internal" href="../prop_tgt/FRAMEWORK.html#prop_tgt:FRAMEWORK" title="FRAMEWORK"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">FRAMEWORK</code></a>, the
<code class="docutils literal notranslate">Headers</code> directory of the framework is also treated as a usage requirement.
This has the same effect as passing the framework directory as an include
directory.
</section>
</section>
<section id="link-libraries-and-generator-expressions">
<h3><a class="toc-backref" href="#id29" role="doc-backlink">Link Libraries and Generator Expressions</a><a class="headerlink" href="#link-libraries-and-generator-expressions" title="Permalink to this heading">¶</a></h3>
Like build specifications, <a class="reference internal" href="../prop_tgt/LINK_LIBRARIES.html#prop_tgt:LINK_LIBRARIES" title="LINK_LIBRARIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">link libraries</code></a> may be
specified with generator expression conditions. However, as consumption of
usage requirements is based on collection from linked dependencies, there is
an additional limitation that the link dependencies must form a &quot;directed
acyclic graph&quot;. That is, if linking to a target is dependent on the value of
a target property, that target property may not be dependent on the linked
dependencies:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(lib1 lib1.cpp)
add_library(lib2 lib2.cpp)
target_link_libraries(lib1 PUBLIC
 $&lt;$&lt;TARGET_PROPERTY:POSITION_INDEPENDENT_CODE&gt;:lib2&gt;
)
add_library(lib3 lib3.cpp)
set_property(TARGET lib3 PROPERTY INTERFACE_POSITION_INDEPENDENT_CODE ON)

add_executable(exe1 exe1.cpp)
target_link_libraries(exe1 lib1 lib3)
</pre></div>
</div>
As the value of the <a class="reference internal" href="../prop_tgt/POSITION_INDEPENDENT_CODE.html#prop_tgt:POSITION_INDEPENDENT_CODE" title="POSITION_INDEPENDENT_CODE"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">POSITION_INDEPENDENT_CODE</code></a> property of
the <code class="docutils literal notranslate">exe1</code> target is dependent on the linked libraries (<code class="docutils literal notranslate">lib3</code>), and the
edge of linking <code class="docutils literal notranslate">exe1</code> is determined by the same
<a class="reference internal" href="../prop_tgt/POSITION_INDEPENDENT_CODE.html#prop_tgt:POSITION_INDEPENDENT_CODE" title="POSITION_INDEPENDENT_CODE"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">POSITION_INDEPENDENT_CODE</code></a> property, the dependency graph above
contains a cycle. <a class="reference internal" href="cmake.1.html#manual:cmake(1)" title="cmake(1)"><code class="xref cmake cmake-manual docutils literal notranslate">cmake(1)</code></a> issues an error message.
</section>
<section id="output-artifacts">
<h3><a class="toc-backref" href="#id30" role="doc-backlink">Output Artifacts</a><a class="headerlink" href="#output-artifacts" title="Permalink to this heading">¶</a></h3>
The buildsystem targets created by the <a class="reference internal" href="../command/add_library.html#command:add_library" title="add_library"><code class="xref cmake cmake-command docutils literal notranslate">add_library()</code></a> and
<a class="reference internal" href="../command/add_executable.html#command:add_executable" title="add_executable"><code class="xref cmake cmake-command docutils literal notranslate">add_executable()</code></a> commands create rules to create binary outputs.
The exact output location of the binaries can only be determined at
generate-time because it can depend on the build-configuration and the
link-language of linked dependencies etc. <code class="docutils literal notranslate">TARGET_FILE</code>,
<code class="docutils literal notranslate">TARGET_LINKER_FILE</code> and related expressions can be used to access the
name and location of generated binaries. These expressions do not work
for <code class="docutils literal notranslate">OBJECT</code> libraries however, as there is no single file generated
by such libraries which is relevant to the expressions.
There are three kinds of output artifacts that may be build by targets
as detailed in the following sections. Their classification differs
between DLL platforms and non-DLL platforms. All Windows-based
systems including Cygwin are DLL platforms.
<section id="runtime-output-artifacts">
<h4><a class="toc-backref" href="#id31" role="doc-backlink">Runtime Output Artifacts</a><a class="headerlink" href="#runtime-output-artifacts" title="Permalink to this heading">¶</a></h4>
A runtime output artifact of a buildsystem target may be:
<ul class="simple">
<li>The executable file (e.g. <code class="docutils literal notranslate">.exe</code>) of an executable target
created by the <a class="reference internal" href="../command/add_executable.html#command:add_executable" title="add_executable"><code class="xref cmake cmake-command docutils literal notranslate">add_executable()</code></a> command.</li>
<li>On DLL platforms: the executable file (e.g. <code class="docutils literal notranslate">.dll</code>) of a shared
library target created by the <a class="reference internal" href="../command/add_library.html#command:add_library" title="add_library"><code class="xref cmake cmake-command docutils literal notranslate">add_library()</code></a> command
with the <code class="docutils literal notranslate">SHARED</code> option.</li>
</ul>
The <a class="reference internal" href="../prop_tgt/RUNTIME_OUTPUT_DIRECTORY.html#prop_tgt:RUNTIME_OUTPUT_DIRECTORY" title="RUNTIME_OUTPUT_DIRECTORY"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">RUNTIME_OUTPUT_DIRECTORY</code></a> and <a class="reference internal" href="../prop_tgt/RUNTIME_OUTPUT_NAME.html#prop_tgt:RUNTIME_OUTPUT_NAME" title="RUNTIME_OUTPUT_NAME"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">RUNTIME_OUTPUT_NAME</code></a>
target properties may be used to control runtime output artifact locations
and names in the build tree.
</section>
<section id="library-output-artifacts">
<h4><a class="toc-backref" href="#id32" role="doc-backlink">Library Output Artifacts</a><a class="headerlink" href="#library-output-artifacts" title="Permalink to this heading">¶</a></h4>
A library output artifact of a buildsystem target may be:
<ul class="simple">
<li>The loadable module file (e.g. <code class="docutils literal notranslate">.dll</code> or <code class="docutils literal notranslate">.so</code>) of a module
library target created by the <a class="reference internal" href="../command/add_library.html#command:add_library" title="add_library"><code class="xref cmake cmake-command docutils literal notranslate">add_library()</code></a> command
with the <code class="docutils literal notranslate">MODULE</code> option.</li>
<li>On non-DLL platforms: the shared library file (e.g. <code class="docutils literal notranslate">.so</code> or <code class="docutils literal notranslate">.dylib</code>)
of a shared library target created by the <a class="reference internal" href="../command/add_library.html#command:add_library" title="add_library"><code class="xref cmake cmake-command docutils literal notranslate">add_library()</code></a>
command with the <code class="docutils literal notranslate">SHARED</code> option.</li>
</ul>
The <a class="reference internal" href="../prop_tgt/LIBRARY_OUTPUT_DIRECTORY.html#prop_tgt:LIBRARY_OUTPUT_DIRECTORY" title="LIBRARY_OUTPUT_DIRECTORY"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">LIBRARY_OUTPUT_DIRECTORY</code></a> and <a class="reference internal" href="../prop_tgt/LIBRARY_OUTPUT_NAME.html#prop_tgt:LIBRARY_OUTPUT_NAME" title="LIBRARY_OUTPUT_NAME"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">LIBRARY_OUTPUT_NAME</code></a>
target properties may be used to control library output artifact locations
and names in the build tree.
</section>
<section id="archive-output-artifacts">
<h4><a class="toc-backref" href="#id33" role="doc-backlink">Archive Output Artifacts</a><a class="headerlink" href="#archive-output-artifacts" title="Permalink to this heading">¶</a></h4>
An archive output artifact of a buildsystem target may be:
<ul class="simple">
<li>The static library file (e.g. <code class="docutils literal notranslate">.lib</code> or <code class="docutils literal notranslate">.a</code>) of a static
library target created by the <a class="reference internal" href="../command/add_library.html#command:add_library" title="add_library"><code class="xref cmake cmake-command docutils literal notranslate">add_library()</code></a> command
with the <code class="docutils literal notranslate">STATIC</code> option.</li>
<li>On DLL platforms: the import library file (e.g. <code class="docutils literal notranslate">.lib</code>) of a shared
library target created by the <a class="reference internal" href="../command/add_library.html#command:add_library" title="add_library"><code class="xref cmake cmake-command docutils literal notranslate">add_library()</code></a> command
with the <code class="docutils literal notranslate">SHARED</code> option. This file is only guaranteed to exist if
the library exports at least one unmanaged symbol.</li>
<li>On DLL platforms: the import library file (e.g. <code class="docutils literal notranslate">.lib</code>) of an
executable target created by the <a class="reference internal" href="../command/add_executable.html#command:add_executable" title="add_executable"><code class="xref cmake cmake-command docutils literal notranslate">add_executable()</code></a> command
when its <a class="reference internal" href="../prop_tgt/ENABLE_EXPORTS.html#prop_tgt:ENABLE_EXPORTS" title="ENABLE_EXPORTS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">ENABLE_EXPORTS</code></a> target property is set.</li>
<li>On AIX: the linker import file (e.g. <code class="docutils literal notranslate">.imp</code>) of an executable target
created by the <a class="reference internal" href="../command/add_executable.html#command:add_executable" title="add_executable"><code class="xref cmake cmake-command docutils literal notranslate">add_executable()</code></a> command when its
<a class="reference internal" href="../prop_tgt/ENABLE_EXPORTS.html#prop_tgt:ENABLE_EXPORTS" title="ENABLE_EXPORTS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">ENABLE_EXPORTS</code></a> target property is set.</li>
</ul>
The <a class="reference internal" href="../prop_tgt/ARCHIVE_OUTPUT_DIRECTORY.html#prop_tgt:ARCHIVE_OUTPUT_DIRECTORY" title="ARCHIVE_OUTPUT_DIRECTORY"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">ARCHIVE_OUTPUT_DIRECTORY</code></a> and <a class="reference internal" href="../prop_tgt/ARCHIVE_OUTPUT_NAME.html#prop_tgt:ARCHIVE_OUTPUT_NAME" title="ARCHIVE_OUTPUT_NAME"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">ARCHIVE_OUTPUT_NAME</code></a>
target properties may be used to control archive output artifact locations
and names in the build tree.
</section>
</section>
<section id="directory-scoped-commands">
<h3><a class="toc-backref" href="#id34" role="doc-backlink">Directory-Scoped Commands</a><a class="headerlink" href="#directory-scoped-commands" title="Permalink to this heading">¶</a></h3>
The <a class="reference internal" href="../command/target_include_directories.html#command:target_include_directories" title="target_include_directories"><code class="xref cmake cmake-command docutils literal notranslate">target_include_directories()</code></a>,
<a class="reference internal" href="../command/target_compile_definitions.html#command:target_compile_definitions" title="target_compile_definitions"><code class="xref cmake cmake-command docutils literal notranslate">target_compile_definitions()</code></a> and
<a class="reference internal" href="../command/target_compile_options.html#command:target_compile_options" title="target_compile_options"><code class="xref cmake cmake-command docutils literal notranslate">target_compile_options()</code></a> commands have an effect on only one
target at a time. The commands <a class="reference internal" href="../command/add_compile_definitions.html#command:add_compile_definitions" title="add_compile_definitions"><code class="xref cmake cmake-command docutils literal notranslate">add_compile_definitions()</code></a>,
<a class="reference internal" href="../command/add_compile_options.html#command:add_compile_options" title="add_compile_options"><code class="xref cmake cmake-command docutils literal notranslate">add_compile_options()</code></a> and <a class="reference internal" href="../command/include_directories.html#command:include_directories" title="include_directories"><code class="xref cmake cmake-command docutils literal notranslate">include_directories()</code></a> have
a similar function, but operate at directory scope instead of target
scope for convenience.
</section>
</section>
<section id="build-configurations">
<h2><a class="toc-backref" href="#id35" role="doc-backlink">Build Configurations</a><a class="headerlink" href="#build-configurations" title="Permalink to this heading">¶</a></h2>
Configurations determine specifications for a certain type of build, such
as <code class="docutils literal notranslate">Release</code> or <code class="docutils literal notranslate">Debug</code>. The way this is specified depends on the type
of <a class="reference internal" href="cmake-generators.7.html#manual:cmake-generators(7)" title="cmake-generators(7)"><code class="xref cmake cmake-manual docutils literal notranslate">generator</code></a> being used. For single
configuration generators like <a class="reference internal" href="cmake-generators.7.html#makefile-generators">Makefile Generators</a> and
<a class="reference internal" href="../generator/Ninja.html#generator:Ninja" title="Ninja"><code class="xref cmake cmake-generator docutils literal notranslate">Ninja</code></a>, the configuration is specified at configure time by the
<a class="reference internal" href="../variable/CMAKE_BUILD_TYPE.html#variable:CMAKE_BUILD_TYPE" title="CMAKE_BUILD_TYPE"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_BUILD_TYPE</code></a> variable. For multi-configuration generators
like <a class="reference internal" href="cmake-generators.7.html#visual-studio-generators">Visual Studio</a>, <a class="reference internal" href="../generator/Xcode.html#generator:Xcode" title="Xcode"><code class="xref cmake cmake-generator docutils literal notranslate">Xcode</code></a>, and
<a class="reference internal" href="../generator/Ninja%20Multi-Config.html#generator:Ninja Multi-Config" title="Ninja Multi-Config"><code class="xref cmake cmake-generator docutils literal notranslate">Ninja Multi-Config</code></a>, the configuration is chosen by the user at
build time and <a class="reference internal" href="../variable/CMAKE_BUILD_TYPE.html#variable:CMAKE_BUILD_TYPE" title="CMAKE_BUILD_TYPE"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_BUILD_TYPE</code></a> is ignored. In the
multi-configuration case, the set of available configurations is specified
at configure time by the <a class="reference internal" href="../variable/CMAKE_CONFIGURATION_TYPES.html#variable:CMAKE_CONFIGURATION_TYPES" title="CMAKE_CONFIGURATION_TYPES"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_CONFIGURATION_TYPES</code></a> variable,
but the actual configuration used cannot be known until the build stage.
This difference is often misunderstood, leading to problematic code like the
following:
<div class="highlight-cmake notranslate"><div class="highlight"><pre># WARNING: This is wrong for multi-config generators because they don&#39;t use
# and typically don&#39;t even set CMAKE_BUILD_TYPE
string(TOLOWER ${CMAKE_BUILD_TYPE} build_type)
if (build_type STREQUAL debug)
 target_compile_definitions(exe1 PRIVATE DEBUG_BUILD)
endif()
</pre></div>
</div>
<a class="reference internal" href="cmake-generator-expressions.7.html#manual:cmake-generator-expressions(7)" title="cmake-generator-expressions(7)"><code class="xref cmake cmake-manual docutils literal notranslate">Generator expressions</code></a> should be
used instead to handle configuration-specific logic correctly, regardless of
the generator used. For example:
<div class="highlight-cmake notranslate"><div class="highlight"><pre># Works correctly for both single and multi-config generators
target_compile_definitions(exe1 PRIVATE
 $&lt;$&lt;CONFIG:Debug&gt;:DEBUG_BUILD&gt;
)
</pre></div>
</div>
In the presence of <a class="reference internal" href="../prop_tgt/IMPORTED.html#prop_tgt:IMPORTED" title="IMPORTED"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">IMPORTED</code></a> targets, the content of
<a class="reference internal" href="../prop_tgt/MAP_IMPORTED_CONFIG_CONFIG.html#prop_tgt:MAP_IMPORTED_CONFIG_&lt;CONFIG&gt;" title="MAP_IMPORTED_CONFIG_&lt;CONFIG&gt;"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">MAP_IMPORTED_CONFIG_DEBUG</code></a> is also
accounted for by the above <a class="reference internal" href="cmake-generator-expressions.7.html#genex:CONFIG" title="CONFIG"><code class="xref cmake cmake-genex docutils literal notranslate">$&lt;CONFIG:Debug&gt;</code></a> expression.
<section id="case-sensitivity">
<h3><a class="toc-backref" href="#id36" role="doc-backlink">Case Sensitivity</a><a class="headerlink" href="#case-sensitivity" title="Permalink to this heading">¶</a></h3>
<a class="reference internal" href="../variable/CMAKE_BUILD_TYPE.html#variable:CMAKE_BUILD_TYPE" title="CMAKE_BUILD_TYPE"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_BUILD_TYPE</code></a> and <a class="reference internal" href="../variable/CMAKE_CONFIGURATION_TYPES.html#variable:CMAKE_CONFIGURATION_TYPES" title="CMAKE_CONFIGURATION_TYPES"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_CONFIGURATION_TYPES</code></a> are
just like other variables in that any string comparisons made with their
values will be case-sensitive. The <a class="reference internal" href="cmake-generator-expressions.7.html#genex:CONFIG" title="CONFIG"><code class="xref cmake cmake-genex docutils literal notranslate">$&lt;CONFIG&gt;</code></a> generator expression also
preserves the casing of the configuration as set by the user or CMake defaults.
For example:
<div class="highlight-cmake notranslate"><div class="highlight"><pre># NOTE: Don&#39;t use these patterns, they are for illustration purposes only.

set(CMAKE_BUILD_TYPE Debug)
if(CMAKE_BUILD_TYPE STREQUAL DEBUG)
 # ... will never get here, &quot;Debug&quot; != &quot;DEBUG&quot;
endif()
add_custom_target(print_config ALL
 # Prints &quot;Config is Debug&quot; in this single-config case
 COMMAND ${CMAKE_COMMAND} -E echo &quot;Config is $&lt;CONFIG&gt;&quot;
 VERBATIM
)

set(CMAKE_CONFIGURATION_TYPES Debug Release)
if(DEBUG IN_LIST CMAKE_CONFIGURATION_TYPES)
 # ... will never get here, &quot;Debug&quot; != &quot;DEBUG&quot;
endif()
</pre></div>
</div>
In contrast, CMake treats the configuration type case-insensitively when
using it internally in places that modify behavior based on the configuration.
For example, the <a class="reference internal" href="cmake-generator-expressions.7.html#genex:CONFIG" title="CONFIG"><code class="xref cmake cmake-genex docutils literal notranslate">$&lt;CONFIG:Debug&gt;</code></a> generator expression will evaluate to 1
for a configuration of not only <code class="docutils literal notranslate">Debug</code>, but also <code class="docutils literal notranslate">DEBUG</code>, <code class="docutils literal notranslate">debug</code> or
even <code class="docutils literal notranslate">DeBuG</code>. Therefore, you can specify configuration types in
<a class="reference internal" href="../variable/CMAKE_BUILD_TYPE.html#variable:CMAKE_BUILD_TYPE" title="CMAKE_BUILD_TYPE"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_BUILD_TYPE</code></a> and <a class="reference internal" href="../variable/CMAKE_CONFIGURATION_TYPES.html#variable:CMAKE_CONFIGURATION_TYPES" title="CMAKE_CONFIGURATION_TYPES"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_CONFIGURATION_TYPES</code></a> with
any mixture of upper and lowercase, although there are strong conventions
(see the next section). If you must test the value in string comparisons,
always convert the value to upper or lowercase first and adjust the test
accordingly.
</section>
<section id="default-and-custom-configurations">
<h3><a class="toc-backref" href="#id37" role="doc-backlink">Default And Custom Configurations</a><a class="headerlink" href="#default-and-custom-configurations" title="Permalink to this heading">¶</a></h3>
By default, CMake defines a number of standard configurations:
<ul class="simple">
<li><code class="docutils literal notranslate">Debug</code></li>
<li><code class="docutils literal notranslate">Release</code></li>
<li><code class="docutils literal notranslate">RelWithDebInfo</code></li>
<li><code class="docutils literal notranslate">MinSizeRel</code></li>
</ul>
In multi-config generators, the <a class="reference internal" href="../variable/CMAKE_CONFIGURATION_TYPES.html#variable:CMAKE_CONFIGURATION_TYPES" title="CMAKE_CONFIGURATION_TYPES"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_CONFIGURATION_TYPES</code></a> variable
will be populated with (potentially a subset of) the above list by default,
unless overridden by the project or user. The actual configuration used is
selected by the user at build time.
For single-config generators, the configuration is specified with the
<a class="reference internal" href="../variable/CMAKE_BUILD_TYPE.html#variable:CMAKE_BUILD_TYPE" title="CMAKE_BUILD_TYPE"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_BUILD_TYPE</code></a> variable at configure time and cannot be changed
at build time. The default value will often be none of the above standard
configurations and will instead be an empty string. A common misunderstanding
is that this is the same as <code class="docutils literal notranslate">Debug</code>, but that is not the case. Users should
always explicitly specify the build type instead to avoid this common problem.
The above standard configuration types provide reasonable behavior on most
platforms, but they can be extended to provide other types. Each configuration
defines a set of compiler and linker flag variables for the language in use.
These variables follow the convention <a class="reference internal" href="../variable/CMAKE_LANG_FLAGS_CONFIG.html#variable:CMAKE_&lt;LANG&gt;_FLAGS_&lt;CONFIG&gt;" title="CMAKE_&lt;LANG&gt;_FLAGS_&lt;CONFIG&gt;"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_&lt;LANG&gt;_FLAGS_&lt;CONFIG&gt;</code></a>,
where <code class="docutils literal notranslate">&lt;CONFIG&gt;</code> is always the uppercase configuration name. When defining
a custom configuration type, make sure these variables are set appropriately,
typically as cache variables.
</section>
</section>
<section id="pseudo-targets">
<h2><a class="toc-backref" href="#id38" role="doc-backlink">Pseudo Targets</a><a class="headerlink" href="#pseudo-targets" title="Permalink to this heading">¶</a></h2>
Some target types do not represent outputs of the buildsystem, but only inputs
such as external dependencies, aliases or other non-build artifacts. Pseudo
targets are not represented in the generated buildsystem.
<section id="imported-targets">
<h3><a class="toc-backref" href="#id39" role="doc-backlink">Imported Targets</a><a class="headerlink" href="#imported-targets" title="Permalink to this heading">¶</a></h3>
An <a class="reference internal" href="../prop_tgt/IMPORTED.html#prop_tgt:IMPORTED" title="IMPORTED"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">IMPORTED</code></a> target represents a pre-existing dependency. Usually
such targets are defined by an upstream package and should be treated as
immutable. After declaring an <a class="reference internal" href="../prop_tgt/IMPORTED.html#prop_tgt:IMPORTED" title="IMPORTED"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">IMPORTED</code></a> target one can adjust its
target properties by using the customary commands such as
<a class="reference internal" href="../command/target_compile_definitions.html#command:target_compile_definitions" title="target_compile_definitions"><code class="xref cmake cmake-command docutils literal notranslate">target_compile_definitions()</code></a>, <a class="reference internal" href="../command/target_include_directories.html#command:target_include_directories" title="target_include_directories"><code class="xref cmake cmake-command docutils literal notranslate">target_include_directories()</code></a>,
<a class="reference internal" href="../command/target_compile_options.html#command:target_compile_options" title="target_compile_options"><code class="xref cmake cmake-command docutils literal notranslate">target_compile_options()</code></a> or <a class="reference internal" href="../command/target_link_libraries.html#command:target_link_libraries" title="target_link_libraries"><code class="xref cmake cmake-command docutils literal notranslate">target_link_libraries()</code></a> just like
with any other regular target.
<a class="reference internal" href="../prop_tgt/IMPORTED.html#prop_tgt:IMPORTED" title="IMPORTED"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">IMPORTED</code></a> targets may have the same usage requirement properties
populated as binary targets, such as
<a class="reference internal" href="../prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html#prop_tgt:INTERFACE_INCLUDE_DIRECTORIES" title="INTERFACE_INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_INCLUDE_DIRECTORIES</code></a>,
<a class="reference internal" href="../prop_tgt/INTERFACE_COMPILE_DEFINITIONS.html#prop_tgt:INTERFACE_COMPILE_DEFINITIONS" title="INTERFACE_COMPILE_DEFINITIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_COMPILE_DEFINITIONS</code></a>,
<a class="reference internal" href="../prop_tgt/INTERFACE_COMPILE_OPTIONS.html#prop_tgt:INTERFACE_COMPILE_OPTIONS" title="INTERFACE_COMPILE_OPTIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_COMPILE_OPTIONS</code></a>,
<a class="reference internal" href="../prop_tgt/INTERFACE_LINK_LIBRARIES.html#prop_tgt:INTERFACE_LINK_LIBRARIES" title="INTERFACE_LINK_LIBRARIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_LINK_LIBRARIES</code></a>, and
<a class="reference internal" href="../prop_tgt/INTERFACE_POSITION_INDEPENDENT_CODE.html#prop_tgt:INTERFACE_POSITION_INDEPENDENT_CODE" title="INTERFACE_POSITION_INDEPENDENT_CODE"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_POSITION_INDEPENDENT_CODE</code></a>.
The <a class="reference internal" href="../prop_tgt/LOCATION.html#prop_tgt:LOCATION" title="LOCATION"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">LOCATION</code></a> may also be read from an IMPORTED target, though there
is rarely reason to do so. Commands such as <a class="reference internal" href="../command/add_custom_command.html#command:add_custom_command" title="add_custom_command"><code class="xref cmake cmake-command docutils literal notranslate">add_custom_command()</code></a> can
transparently use an <a class="reference internal" href="../prop_tgt/IMPORTED.html#prop_tgt:IMPORTED" title="IMPORTED"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">IMPORTED</code></a> <a class="reference internal" href="../prop_tgt/TYPE.html#prop_tgt:TYPE" title="TYPE"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">EXECUTABLE</code></a> target
as a <code class="docutils literal notranslate">COMMAND</code> executable.
The scope of the definition of an <a class="reference internal" href="../prop_tgt/IMPORTED.html#prop_tgt:IMPORTED" title="IMPORTED"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">IMPORTED</code></a> target is the directory
where it was defined. It may be accessed and used from subdirectories, but
not from parent directories or sibling directories. The scope is similar to
the scope of a cmake variable.
It is also possible to define a <code class="docutils literal notranslate">GLOBAL</code> <a class="reference internal" href="../prop_tgt/IMPORTED.html#prop_tgt:IMPORTED" title="IMPORTED"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">IMPORTED</code></a> target which is
accessible globally in the buildsystem.
See the <a class="reference internal" href="cmake-packages.7.html#manual:cmake-packages(7)" title="cmake-packages(7)"><code class="xref cmake cmake-manual docutils literal notranslate">cmake-packages(7)</code></a> manual for more on creating packages
with <a class="reference internal" href="../prop_tgt/IMPORTED.html#prop_tgt:IMPORTED" title="IMPORTED"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">IMPORTED</code></a> targets.
</section>
<section id="alias-targets">
<h3><a class="toc-backref" href="#id40" role="doc-backlink">Alias Targets</a><a class="headerlink" href="#alias-targets" title="Permalink to this heading">¶</a></h3>
An <code class="docutils literal notranslate">ALIAS</code> target is a name which may be used interchangeably with
a binary target name in read-only contexts. A primary use-case for <code class="docutils literal notranslate">ALIAS</code>
targets is for example or unit test executables accompanying a library, which
may be part of the same buildsystem or built separately based on user
configuration.
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(lib1 lib1.cpp)
install(TARGETS lib1 EXPORT lib1Export ${dest_args})
install(EXPORT lib1Export NAMESPACE Upstream:: ${other_args})

add_library(Upstream::lib1 ALIAS lib1)
</pre></div>
</div>
In another directory, we can link unconditionally to the <code class="docutils literal notranslate">Upstream::lib1</code>
target, which may be an <a class="reference internal" href="../prop_tgt/IMPORTED.html#prop_tgt:IMPORTED" title="IMPORTED"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">IMPORTED</code></a> target from a package, or an
<code class="docutils literal notranslate">ALIAS</code> target if built as part of the same buildsystem.
<div class="highlight-cmake notranslate"><div class="highlight"><pre>if (NOT TARGET Upstream::lib1)
 find_package(lib1 REQUIRED)
endif()
add_executable(exe1 exe1.cpp)
target_link_libraries(exe1 Upstream::lib1)
</pre></div>
</div>
<code class="docutils literal notranslate">ALIAS</code> targets are not mutable, installable or exportable. They are
entirely local to the buildsystem description. A name can be tested for
whether it is an <code class="docutils literal notranslate">ALIAS</code> name by reading the <a class="reference internal" href="../prop_tgt/ALIASED_TARGET.html#prop_tgt:ALIASED_TARGET" title="ALIASED_TARGET"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">ALIASED_TARGET</code></a>
property from it:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>get_target_property(_aliased Upstream::lib1 ALIASED_TARGET)
if(_aliased)
 message(STATUS &quot;The name Upstream::lib1 is an ALIAS for ${_aliased}.&quot;)
endif()
</pre></div>
</div>
</section>
<section id="interface-libraries">
<h3><a class="toc-backref" href="#id41" role="doc-backlink">Interface Libraries</a><a class="headerlink" href="#interface-libraries" title="Permalink to this heading">¶</a></h3>
An <code class="docutils literal notranslate">INTERFACE</code> library target does not compile sources and does not
produce a library artifact on disk, so it has no <a class="reference internal" href="../prop_tgt/LOCATION.html#prop_tgt:LOCATION" title="LOCATION"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">LOCATION</code></a>.
It may specify usage requirements such as
<a class="reference internal" href="../prop_tgt/INTERFACE_INCLUDE_DIRECTORIES.html#prop_tgt:INTERFACE_INCLUDE_DIRECTORIES" title="INTERFACE_INCLUDE_DIRECTORIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_INCLUDE_DIRECTORIES</code></a>,
<a class="reference internal" href="../prop_tgt/INTERFACE_COMPILE_DEFINITIONS.html#prop_tgt:INTERFACE_COMPILE_DEFINITIONS" title="INTERFACE_COMPILE_DEFINITIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_COMPILE_DEFINITIONS</code></a>,
<a class="reference internal" href="../prop_tgt/INTERFACE_COMPILE_OPTIONS.html#prop_tgt:INTERFACE_COMPILE_OPTIONS" title="INTERFACE_COMPILE_OPTIONS"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_COMPILE_OPTIONS</code></a>,
<a class="reference internal" href="../prop_tgt/INTERFACE_LINK_LIBRARIES.html#prop_tgt:INTERFACE_LINK_LIBRARIES" title="INTERFACE_LINK_LIBRARIES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_LINK_LIBRARIES</code></a>,
<a class="reference internal" href="../prop_tgt/INTERFACE_SOURCES.html#prop_tgt:INTERFACE_SOURCES" title="INTERFACE_SOURCES"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_SOURCES</code></a>,
and <a class="reference internal" href="../prop_tgt/INTERFACE_POSITION_INDEPENDENT_CODE.html#prop_tgt:INTERFACE_POSITION_INDEPENDENT_CODE" title="INTERFACE_POSITION_INDEPENDENT_CODE"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">INTERFACE_POSITION_INDEPENDENT_CODE</code></a>.
Only the <code class="docutils literal notranslate">INTERFACE</code> modes of the <a class="reference internal" href="../command/target_include_directories.html#command:target_include_directories" title="target_include_directories"><code class="xref cmake cmake-command docutils literal notranslate">target_include_directories()</code></a>,
<a class="reference internal" href="../command/target_compile_definitions.html#command:target_compile_definitions" title="target_compile_definitions"><code class="xref cmake cmake-command docutils literal notranslate">target_compile_definitions()</code></a>, <a class="reference internal" href="../command/target_compile_options.html#command:target_compile_options" title="target_compile_options"><code class="xref cmake cmake-command docutils literal notranslate">target_compile_options()</code></a>,
<a class="reference internal" href="../command/target_sources.html#command:target_sources" title="target_sources"><code class="xref cmake cmake-command docutils literal notranslate">target_sources()</code></a>, and <a class="reference internal" href="../command/target_link_libraries.html#command:target_link_libraries" title="target_link_libraries"><code class="xref cmake cmake-command docutils literal notranslate">target_link_libraries()</code></a> commands
may be used with <code class="docutils literal notranslate">INTERFACE</code> libraries.
Since CMake 3.19, an <code class="docutils literal notranslate">INTERFACE</code> library target may optionally contain
source files. An interface library that contains source files will be
included as a build target in the generated buildsystem. It does not
compile sources, but may contain custom commands to generate other sources.
Additionally, IDEs will show the source files as part of the target for
interactive reading and editing.
A primary use-case for <code class="docutils literal notranslate">INTERFACE</code> libraries is header-only libraries.
Since CMake 3.23, header files may be associated with a library by adding
them to a header set using the <a class="reference internal" href="../command/target_sources.html#command:target_sources" title="target_sources"><code class="xref cmake cmake-command docutils literal notranslate">target_sources()</code></a> command:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(Eigen INTERFACE)

target_sources(Eigen PUBLIC
 FILE_SET HEADERS
 BASE_DIRS src
 FILES src/eigen.h src/vector.h src/matrix.h
)

add_library(enable_rtti INTERFACE)
target_compile_options(enable_rtti INTERFACE
 $&lt;$&lt;OR:$&lt;COMPILER_ID:GNU&gt;,$&lt;COMPILER_ID:Clang&gt;&gt;:-rtti&gt;
)

target_sources(Eigen INTERFACE
 FILE_SET HEADERS
 BASE_DIRS src
 FILES src/eigen.h src/vector.h src/matrix.h
)

install(TARGETS Eigen EXPORT eigenExport
 FILE_SET HEADERS DESTINATION include/Eigen)
install(EXPORT eigenExport NAMESPACE Upstream::
 DESTINATION lib/cmake/Eigen
)
</pre></div>
</div>
Here, the headers defined in the header set are installed to <code class="docutils literal notranslate">include/Eigen</code>.
The install destination automatically becomes an include directory that is a
usage requirement for consumers.
</section>
</section>
</section>

<div class="clearer"></div>
 </div>
 </div>
 </div>
 <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
 <div class="sphinxsidebarwrapper">
 <div>
 <h3><a href="../index.html">Table of Contents</a></h3>
 <ul>
<li><a class="reference internal" href="#">cmake-buildsystem(7)</a><ul>
<li><a class="reference internal" href="#introduction">Introduction</a></li>
<li><a class="reference internal" href="#binary-targets">Binary Targets</a><ul>
<li><a class="reference internal" href="#binary-executables">Binary Executables</a></li>
<li><a class="reference internal" href="#binary-library-types">Binary Library Types</a><ul>
<li><a class="reference internal" href="#normal-libraries">Normal Libraries</a><ul>
<li><a class="reference internal" href="#apple-frameworks">Apple Frameworks</a></li>
</ul>
</li>
<li><a class="reference internal" href="#object-libraries">Object Libraries</a></li>
</ul>
</li>
</ul>
</li>
<li><a class="reference internal" href="#build-specification-and-usage-requirements">Build Specification and Usage Requirements</a><ul>
<li><a class="reference internal" href="#target-properties">Target Properties</a></li>
<li><a class="reference internal" href="#transitive-usage-requirements">Transitive Usage Requirements</a></li>
<li><a class="reference internal" href="#compatible-interface-properties">Compatible Interface Properties</a></li>
<li><a class="reference internal" href="#property-origin-debugging">Property Origin Debugging</a></li>
<li><a class="reference internal" href="#build-specification-with-generator-expressions">Build Specification with Generator Expressions</a><ul>
<li><a class="reference internal" href="#include-directories-and-usage-requirements">Include Directories and Usage Requirements</a></li>
</ul>
</li>
<li><a class="reference internal" href="#link-libraries-and-generator-expressions">Link Libraries and Generator Expressions</a></li>
<li><a class="reference internal" href="#output-artifacts">Output Artifacts</a><ul>
<li><a class="reference internal" href="#runtime-output-artifacts">Runtime Output Artifacts</a></li>
<li><a class="reference internal" href="#library-output-artifacts">Library Output Artifacts</a></li>
<li><a class="reference internal" href="#archive-output-artifacts">Archive Output Artifacts</a></li>
</ul>
</li>
<li><a class="reference internal" href="#directory-scoped-commands">Directory-Scoped Commands</a></li>
</ul>
</li>
<li><a class="reference internal" href="#build-configurations">Build Configurations</a><ul>
<li><a class="reference internal" href="#case-sensitivity">Case Sensitivity</a></li>
<li><a class="reference internal" href="#default-and-custom-configurations">Default And Custom Configurations</a></li>
</ul>
</li>
<li><a class="reference internal" href="#pseudo-targets">Pseudo Targets</a><ul>
<li><a class="reference internal" href="#imported-targets">Imported Targets</a></li>
<li><a class="reference internal" href="#alias-targets">Alias Targets</a></li>
<li><a class="reference internal" href="#interface-libraries">Interface Libraries</a></li>
</ul>
</li>
</ul>
</li>
</ul>

</div>
 <div>
 <h4>Previous topic</h4>
 <a href="ccmake.1.html"
 title="previous chapter">ccmake(1)</a>
 </div>
 <div>
 <h4>Next topic</h4>
 <a href="cmake-commands.7.html"
 title="next chapter">cmake-commands(7)</a>
 </div>
 <div role="note" aria-label="source link">
 <h3>This Page</h3>
 <ul class="this-page-menu">
 <li><a href="../_sources/manual/cmake-buildsystem.7.rst.txt"
 rel="nofollow">Show Source</a></li>
 </ul>
 </div>
<div id="searchbox" style="display: none" role="search">
 <h3 id="searchlabel">Quick search</h3>
 <div class="searchformwrapper">
 <form class="search" action="../search.html" method="get">
 <input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
 <input type="submit" value="Go" />
 </form>
 </div>
</div>
<script>document.getElementById('searchbox').style.display = "block"</script>
 </div>
 </div>
 <div class="clearer"></div>
 </div>
 <div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 >index</a></li>
 <li class="right" >
 <a href="cmake-commands.7.html" title="cmake-commands(7)"
 >next</a> |</li>
 <li class="right" >
 <a href="ccmake.1.html" title="ccmake(1)"
 >previous</a> |</li>
 <li>
 <img src="../_static/cmake-logo-16.png" alt=""
 style="vertical-align: middle; margin-top: -2px" />
 </li>
 <li>
 <a href="https://cmake.org/">CMake</a> &#187;
 </li>
 <li>
 <a href="../index.html">3.26.3 Documentation</a> &#187;
 </li>

<li class="nav-item nav-item-this"><a href="">cmake-buildsystem(7)</a></li> 
 </ul>
 </div>

<div class="footer" role="contentinfo">
 &#169; Copyright 2000-2023 Kitware, Inc. and Contributors.
 Created using <a href="https://www.sphinx-doc.org/">Sphinx</a> 5.0.2.
 </div>
 </body>
</html>