OXIESEC PANEL

Name	Size	Modified	Perms
📁 ..	-	04/04/2023 07:10:48 PM	rwxr-xr-x
📄 add_compile_definitions.html	8.97 KB	04/04/2023 07:04:57 PM	rw-r--r--
📄 add_compile_options.html	13.11 KB	04/04/2023 07:04:57 PM	rw-r--r--
📄 add_custom_command.html	67.2 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 add_custom_target.html	26.7 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 add_definitions.html	9.72 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 add_dependencies.html	8.79 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 add_executable.html	20.23 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 add_library.html	43.25 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 add_link_options.html	17.79 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 add_subdirectory.html	8.85 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 add_test.html	17.09 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 aux_source_directory.html	6.45 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 block.html	13.15 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 break.html	5.97 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 build_command.html	10.66 KB	04/04/2023 07:04:58 PM	rw-r--r--
📄 build_name.html	6.43 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 cmake_host_system_information.html	38.46 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 cmake_language.html	59.74 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 cmake_minimum_required.html	13.56 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 cmake_parse_arguments.html	18.62 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 cmake_path.html	80.45 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 cmake_policy.html	23.14 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 configure_file.html	20.36 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 continue.html	6.15 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 create_test_sourcelist.html	7.61 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 ctest_build.html	14.87 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 ctest_configure.html	10.28 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 ctest_coverage.html	9.93 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 ctest_empty_binary_directory.html	5.54 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 ctest_memcheck.html	11.73 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 ctest_read_custom_files.html	5.78 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 ctest_run_script.html	6.72 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 ctest_sleep.html	5.66 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 ctest_start.html	14.68 KB	04/04/2023 07:04:59 PM	rw-r--r--
📄 ctest_submit.html	16.18 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 ctest_test.html	38.64 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 ctest_update.html	8.79 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 ctest_upload.html	6.7 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 define_property.html	15.53 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 else.html	5.35 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 elseif.html	5.44 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 enable_language.html	10.08 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 enable_testing.html	6.04 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 endblock.html	5.66 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 endforeach.html	5.88 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 endfunction.html	5.85 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 endif.html	5.71 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 endmacro.html	5.79 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 endwhile.html	5.79 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 exec_program.html	7.52 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 execute_process.html	20.95 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 export.html	19.49 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 export_library_dependencies.html	8.01 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 file.html	128.25 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 find_file.html	39.65 KB	04/04/2023 07:05:00 PM	rw-r--r--
📄 find_library.html	46.52 KB	04/04/2023 07:05:01 PM	rw-r--r--
📄 find_package.html	91.29 KB	04/04/2023 07:05:01 PM	rw-r--r--
📄 find_path.html	40.22 KB	04/04/2023 07:05:01 PM	rw-r--r--
📄 find_program.html	37.17 KB	04/04/2023 07:05:01 PM	rw-r--r--
📄 fltk_wrap_ui.html	5.8 KB	04/04/2023 07:05:01 PM	rw-r--r--
📄 foreach.html	18.65 KB	04/04/2023 07:05:01 PM	rw-r--r--
📄 function.html	12.42 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 get_cmake_property.html	8.05 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 get_directory_property.html	9.08 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 get_filename_component.html	12.57 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 get_property.html	15.95 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 get_source_file_property.html	11.47 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 get_target_property.html	9.1 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 get_test_property.html	8.06 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 if.html	41.89 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 include.html	8.04 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 include_directories.html	10.54 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 include_external_msproject.html	8.14 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 include_guard.html	8.85 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 include_regular_expression.html	6.14 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 install.html	126.44 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 install_files.html	9.13 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 install_programs.html	9.09 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 install_targets.html	7 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 link_directories.html	11.99 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 link_libraries.html	7.36 KB	04/04/2023 07:05:02 PM	rw-r--r--
📄 list.html	35.79 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 load_cache.html	6.78 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 load_command.html	6.61 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 macro.html	20.49 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 make_directory.html	5.77 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 mark_as_advanced.html	6.73 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 math.html	9.01 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 message.html	27.67 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 option.html	6.48 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 output_required_files.html	6.59 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 project.html	30.84 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 qt_wrap_cpp.html	7.2 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 qt_wrap_ui.html	7.43 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 remove.html	6 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 remove_definitions.html	6.15 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 return.html	16.06 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 separate_arguments.html	11.04 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 set.html	18.35 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 set_directory_properties.html	7.58 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 set_property.html	17.74 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 set_source_files_properties.html	10.63 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 set_target_properties.html	8.33 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 set_tests_properties.html	7.98 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 site_name.html	5.46 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 source_group.html	10.97 KB	04/04/2023 07:05:03 PM	rw-r--r--
📄 string.html	64.24 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 subdir_depends.html	5.69 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 subdirs.html	7.51 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 target_compile_definitions.html	16.09 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 target_compile_features.html	14.47 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 target_compile_options.html	18.02 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 target_include_directories.html	22.39 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 target_link_directories.html	16.03 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 target_link_libraries.html	60.83 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 target_link_options.html	23.66 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 target_precompile_headers.html	24.42 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 target_sources.html	38.35 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 try_compile.html	57.47 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 try_run.html	24.62 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 unset.html	9.21 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 use_mangled_mesa.html	5.91 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 utility_source.html	6.78 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 variable_requires.html	6.84 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 variable_watch.html	8.98 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 while.html	9.14 KB	04/04/2023 07:05:04 PM	rw-r--r--
📄 write_file.html	7.25 KB	04/04/2023 07:05:04 PM	rw-r--r--

Editing: add_custom_command.html

<!DOCTYPE html>

<title>add_custom_command &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="add_custom_target.html" title="add_custom_target"
 accesskey="N">next</a> |</li>
 <li class="right" >
 <a href="add_compile_options.html" title="add_compile_options"
 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-1"><a href="../manual/cmake-commands.7.html" accesskey="U">cmake-commands(7)</a> &#187;</li>
 <li class="nav-item nav-item-this"><a href="">add_custom_command</a></li> 
 </ul>
 </div>

<div class="document">
 <div class="documentwrapper">
 <div class="bodywrapper">
 <div class="body" role="main">
 
 <section id="add-custom-command">
<h1>add_custom_command<a class="headerlink" href="#add-custom-command" title="Permalink to this heading">¶</a></h1>
Add a custom build rule to the generated build system.
There are two main signatures for <code class="docutils literal notranslate">add_custom_command</code>.
<section id="generating-files">
<h2>Generating Files<a class="headerlink" href="#generating-files" title="Permalink to this heading">¶</a></h2>
The first signature is for adding a custom command to produce an output:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_custom_command(OUTPUT output1 [output2 ...]
 COMMAND command1 [ARGS] [args1...]
 [COMMAND command2 [ARGS] [args2...] ...]
 [MAIN_DEPENDENCY depend]
 [DEPENDS [depends...]]
 [BYPRODUCTS [files...]]
 [IMPLICIT_DEPENDS &lt;lang1&gt; depend1
 [&lt;lang2&gt; depend2] ...]
 [WORKING_DIRECTORY dir]
 [COMMENT comment]
 [DEPFILE depfile]
 [JOB_POOL job_pool]
 [VERBATIM] [APPEND] [USES_TERMINAL]
 [COMMAND_EXPAND_LISTS])
</pre></div>
</div>
This defines a command to generate specified <code class="docutils literal notranslate">OUTPUT</code> file(s).
A target created in the same directory (<code class="docutils literal notranslate">CMakeLists.txt</code> file)
that specifies any output of the custom command as a source file
is given a rule to generate the file using the command at build time.
Do not list the output in more than one independent target that
may build in parallel or the instances of the rule may conflict.
Instead, use the <a class="reference internal" href="add_custom_target.html#command:add_custom_target" title="add_custom_target"><code class="xref cmake cmake-command docutils literal notranslate">add_custom_target()</code></a> command to drive the
command and make the other targets depend on that one. See the
<a class="reference internal" href="#example-generating-files-for-multiple-targets">Example: Generating Files for Multiple Targets</a> below.
The options are:
<dl>
<dt><code class="docutils literal notranslate">APPEND</code></dt><dd>Append the <code class="docutils literal notranslate">COMMAND</code> and <code class="docutils literal notranslate">DEPENDS</code> option values to the custom
command for the first output specified. There must have already
been a previous call to this command with the same output.
If the previous call specified the output via a generator expression,
the output specified by the current call must match in at least one
configuration after evaluating generator expressions. In this case,
the appended commands and dependencies apply to all configurations.
The <code class="docutils literal notranslate">COMMENT</code>, <code class="docutils literal notranslate">MAIN_DEPENDENCY</code>, and <code class="docutils literal notranslate">WORKING_DIRECTORY</code>
options are currently ignored when APPEND is given, but may be
used in the future.
</dd>
<dt><code class="docutils literal notranslate">BYPRODUCTS</code></dt><dd><div class="versionadded">
New in version 3.2.
</div>
Specify the files the command is expected to produce but whose
modification time may or may not be newer than the dependencies.
If a byproduct name is a relative path it will be interpreted
relative to the build tree directory corresponding to the
current source directory.
Each byproduct file will be marked with the <a class="reference internal" href="../prop_sf/GENERATED.html#prop_sf:GENERATED" title="GENERATED"><code class="xref cmake cmake-prop_sf docutils literal notranslate">GENERATED</code></a>
source file property automatically.
See policy <a class="reference internal" href="../policy/CMP0058.html#policy:CMP0058" title="CMP0058"><code class="xref cmake cmake-policy docutils literal notranslate">CMP0058</code></a> for the motivation behind this feature.
Explicit specification of byproducts is supported by the
<a class="reference internal" href="../generator/Ninja.html#generator:Ninja" title="Ninja"><code class="xref cmake cmake-generator docutils literal notranslate">Ninja</code></a> generator to tell the <code class="docutils literal notranslate">ninja</code> build tool
how to regenerate byproducts when they are missing. It is
also useful when other build rules (e.g. custom commands)
depend on the byproducts. Ninja requires a build rule for any
generated file on which another rule depends even if there are
order-only dependencies to ensure the byproducts will be
available before their dependents build.
The <a class="reference internal" href="../manual/cmake-generators.7.html#makefile-generators">Makefile Generators</a> will remove <code class="docutils literal notranslate">BYPRODUCTS</code> and other
<a class="reference internal" href="../prop_sf/GENERATED.html#prop_sf:GENERATED" title="GENERATED"><code class="xref cmake cmake-prop_sf docutils literal notranslate">GENERATED</code></a> files during <code class="docutils literal notranslate">make clean</code>.
<div class="versionadded">
New in version 3.20: Arguments to <code class="docutils literal notranslate">BYPRODUCTS</code> may use a restricted set of
<a class="reference internal" href="../manual/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>.
<a class="reference internal" href="../manual/cmake-generator-expressions.7.html#target-dependent-queries">Target-dependent expressions</a> are not
permitted.
</div>
</dd>
<dt><code class="docutils literal notranslate">COMMAND</code></dt><dd>Specify the command-line(s) to execute at build time.
If more than one <code class="docutils literal notranslate">COMMAND</code> is specified they will be executed in order,
but not necessarily composed into a stateful shell or batch script.
(To run a full script, use the <a class="reference internal" href="configure_file.html#command:configure_file" title="configure_file"><code class="xref cmake cmake-command docutils literal notranslate">configure_file()</code></a> command or the
<a class="reference internal" href="file.html#command:file" title="file"><code class="xref cmake cmake-command docutils literal notranslate">file(GENERATE)</code></a> command to create it, and then specify
a <code class="docutils literal notranslate">COMMAND</code> to launch it.)
The optional <code class="docutils literal notranslate">ARGS</code> argument is for backward compatibility and
will be ignored.
If <code class="docutils literal notranslate">COMMAND</code> specifies an executable target name (created by the
<a class="reference internal" href="add_executable.html#command:add_executable" title="add_executable"><code class="xref cmake cmake-command docutils literal notranslate">add_executable()</code></a> command), it will automatically be replaced
by the location of the executable created at build time if either of
the following is true:
<ul>
<li>The target is not being cross-compiled (i.e. the
<a class="reference internal" href="../variable/CMAKE_CROSSCOMPILING.html#variable:CMAKE_CROSSCOMPILING" title="CMAKE_CROSSCOMPILING"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_CROSSCOMPILING</code></a> variable is not set to true).</li>
<li><div class="versionadded">
New in version 3.6: The target is being cross-compiled and an emulator is provided (i.e.
its <a class="reference internal" href="../prop_tgt/CROSSCOMPILING_EMULATOR.html#prop_tgt:CROSSCOMPILING_EMULATOR" title="CROSSCOMPILING_EMULATOR"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">CROSSCOMPILING_EMULATOR</code></a> target property is set).
In this case, the contents of <a class="reference internal" href="../prop_tgt/CROSSCOMPILING_EMULATOR.html#prop_tgt:CROSSCOMPILING_EMULATOR" title="CROSSCOMPILING_EMULATOR"><code class="xref cmake cmake-prop_tgt docutils literal notranslate">CROSSCOMPILING_EMULATOR</code></a> will be
prepended to the command before the location of the target executable.
</div>
</li>
</ul>
If neither of the above conditions are met, it is assumed that the
command name is a program to be found on the <code class="docutils literal notranslate">PATH</code> at build time.
Arguments to <code class="docutils literal notranslate">COMMAND</code> may use
<a class="reference internal" href="../manual/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>.
Use the <a class="reference internal" href="../manual/cmake-generator-expressions.7.html#genex:TARGET_FILE" title="TARGET_FILE"><code class="xref cmake cmake-genex docutils literal notranslate">TARGET_FILE</code></a> generator expression to refer to the location
of a target later in the command line (i.e. as a command argument rather
than as the command to execute).
Whenever one of the following target based generator expressions are used as
a command to execute or is mentioned in a command argument, a target-level
dependency will be added automatically so that the mentioned target will be
built before any target using this custom command
(see policy <a class="reference internal" href="../policy/CMP0112.html#policy:CMP0112" title="CMP0112"><code class="xref cmake cmake-policy docutils literal notranslate">CMP0112</code></a>).
<blockquote>
<div><ul class="simple">
<li><code class="docutils literal notranslate">TARGET_FILE</code></li>
<li><code class="docutils literal notranslate">TARGET_LINKER_FILE</code></li>
<li><code class="docutils literal notranslate">TARGET_SONAME_FILE</code></li>
<li><code class="docutils literal notranslate">TARGET_PDB_FILE</code></li>
</ul>
</div></blockquote>
This target-level dependency does NOT add a file-level dependency that would
cause the custom command to re-run whenever the executable is recompiled.
List target names with the <code class="docutils literal notranslate">DEPENDS</code> option to add such file-level
dependencies.
</dd>
<dt><code class="docutils literal notranslate">COMMENT</code></dt><dd>Display the given message before the commands are executed at
build time.
<div class="versionadded">
New in version 3.26: Arguments to <code class="docutils literal notranslate">COMMENT</code> may use
<a class="reference internal" href="../manual/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>.
</div>
</dd>
<dt><code class="docutils literal notranslate">DEPENDS</code></dt><dd>Specify files on which the command depends. Each argument is converted
to a dependency as follows:
<ol class="arabic simple">
<li>If the argument is the name of a target (created by the
<a class="reference internal" href="add_custom_target.html#command:add_custom_target" title="add_custom_target"><code class="xref cmake cmake-command docutils literal notranslate">add_custom_target()</code></a>, <a class="reference internal" href="add_executable.html#command:add_executable" title="add_executable"><code class="xref cmake cmake-command docutils literal notranslate">add_executable()</code></a>, or
<a class="reference internal" href="add_library.html#command:add_library" title="add_library"><code class="xref cmake cmake-command docutils literal notranslate">add_library()</code></a> command) a target-level dependency is
created to make sure the target is built before any target
using this custom command. Additionally, if the target is an
executable or library, a file-level dependency is created to
cause the custom command to re-run whenever the target is
recompiled.</li>
<li>If the argument is an absolute path, a file-level dependency
is created on that path.</li>
<li>If the argument is the name of a source file that has been
added to a target or on which a source file property has been set,
a file-level dependency is created on that source file.</li>
<li>If the argument is a relative path and it exists in the current
source directory, a file-level dependency is created on that
file in the current source directory.</li>
<li>Otherwise, a file-level dependency is created on that path relative
to the current binary directory.</li>
</ol>
If any dependency is an <code class="docutils literal notranslate">OUTPUT</code> of another custom command in the same
directory (<code class="docutils literal notranslate">CMakeLists.txt</code> file), CMake automatically brings the other
custom command into the target in which this command is built.
<div class="versionadded">
New in version 3.16: A target-level dependency is added if any dependency is listed as
<code class="docutils literal notranslate">BYPRODUCTS</code> of a target or any of its build events in the same
directory to ensure the byproducts will be available.
</div>
If <code class="docutils literal notranslate">DEPENDS</code> is not specified, the command will run whenever
the <code class="docutils literal notranslate">OUTPUT</code> is missing; if the command does not actually
create the <code class="docutils literal notranslate">OUTPUT</code>, the rule will always run.
<div class="versionadded">
New in version 3.1: Arguments to <code class="docutils literal notranslate">DEPENDS</code> may use
<a class="reference internal" href="../manual/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>.
</div>
</dd>
<dt><code class="docutils literal notranslate">COMMAND_EXPAND_LISTS</code></dt><dd><div class="versionadded">
New in version 3.8.
</div>
Lists in <code class="docutils literal notranslate">COMMAND</code> arguments will be expanded, including those
created with
<a class="reference internal" href="../manual/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>,
allowing <code class="docutils literal notranslate">COMMAND</code> arguments such as
<code class="docutils literal notranslate">${CC} &quot;-I$&lt;JOIN:$&lt;TARGET_PROPERTY:foo,INCLUDE_DIRECTORIES&gt;,;-I&gt;&quot; foo.cc</code>
to be properly expanded.
</dd>
<dt><code class="docutils literal notranslate">IMPLICIT_DEPENDS</code></dt><dd>Request scanning of implicit dependencies of an input file.
The language given specifies the programming language whose
corresponding dependency scanner should be used.
Currently only <code class="docutils literal notranslate">C</code> and <code class="docutils literal notranslate">CXX</code> language scanners are supported.
The language has to be specified for every file in the
<code class="docutils literal notranslate">IMPLICIT_DEPENDS</code> list. Dependencies discovered from the
scanning are added to those of the custom command at build time.
Note that the <code class="docutils literal notranslate">IMPLICIT_DEPENDS</code> option is currently supported
only for Makefile generators and will be ignored by other generators.
<div class="admonition note">
Note
This option cannot be specified at the same time as <code class="docutils literal notranslate">DEPFILE</code> option.
</div>
</dd>
<dt><code class="docutils literal notranslate">JOB_POOL</code></dt><dd><div class="versionadded">
New in version 3.15.
</div>
Specify a <a class="reference internal" href="../prop_gbl/JOB_POOLS.html#prop_gbl:JOB_POOLS" title="JOB_POOLS"><code class="xref cmake cmake-prop_gbl docutils literal notranslate">pool</code></a> for the <a class="reference internal" href="../generator/Ninja.html#generator:Ninja" title="Ninja"><code class="xref cmake cmake-generator docutils literal notranslate">Ninja</code></a>
generator. Incompatible with <code class="docutils literal notranslate">USES_TERMINAL</code>, which implies
the <code class="docutils literal notranslate">console</code> pool.
Using a pool that is not defined by <a class="reference internal" href="../prop_gbl/JOB_POOLS.html#prop_gbl:JOB_POOLS" title="JOB_POOLS"><code class="xref cmake cmake-prop_gbl docutils literal notranslate">JOB_POOLS</code></a> causes
an error by ninja at build time.
</dd>
<dt><code class="docutils literal notranslate">MAIN_DEPENDENCY</code></dt><dd>Specify the primary input source file to the command. This is
treated just like any value given to the <code class="docutils literal notranslate">DEPENDS</code> option
but also suggests to Visual Studio generators where to hang
the custom command. Each source file may have at most one command
specifying it as its main dependency. A compile command (i.e. for a
library or an executable) counts as an implicit main dependency which
gets silently overwritten by a custom command specification.
</dd>
<dt><code class="docutils literal notranslate">OUTPUT</code></dt><dd>Specify the output files the command is expected to produce.
Each output file will be marked with the <a class="reference internal" href="../prop_sf/GENERATED.html#prop_sf:GENERATED" title="GENERATED"><code class="xref cmake cmake-prop_sf docutils literal notranslate">GENERATED</code></a>
source file property automatically.
If the output of the custom command is not actually created
as a file on disk it should be marked with the <a class="reference internal" href="../prop_sf/SYMBOLIC.html#prop_sf:SYMBOLIC" title="SYMBOLIC"><code class="xref cmake cmake-prop_sf docutils literal notranslate">SYMBOLIC</code></a>
source file property.
If an output file name is a relative path, its absolute path is
determined by interpreting it relative to:
<ol class="arabic simple">
<li>the build directory corresponding to the current source directory
(<a class="reference internal" href="../variable/CMAKE_CURRENT_BINARY_DIR.html#variable:CMAKE_CURRENT_BINARY_DIR" title="CMAKE_CURRENT_BINARY_DIR"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_CURRENT_BINARY_DIR</code></a>), or</li>
<li>the current source directory (<a class="reference internal" href="../variable/CMAKE_CURRENT_SOURCE_DIR.html#variable:CMAKE_CURRENT_SOURCE_DIR" title="CMAKE_CURRENT_SOURCE_DIR"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_CURRENT_SOURCE_DIR</code></a>).</li>
</ol>
The path in the build directory is preferred unless the path in the
source tree is mentioned as an absolute source file path elsewhere
in the current directory.
<div class="versionadded">
New in version 3.20: Arguments to <code class="docutils literal notranslate">OUTPUT</code> may use a restricted set of
<a class="reference internal" href="../manual/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>.
<a class="reference internal" href="../manual/cmake-generator-expressions.7.html#target-dependent-queries">Target-dependent expressions</a> are not
permitted.
</div>
</dd>
<dt><code class="docutils literal notranslate">USES_TERMINAL</code></dt><dd><div class="versionadded">
New in version 3.2.
</div>
The command will be given direct access to the terminal if possible.
With the <a class="reference internal" href="../generator/Ninja.html#generator:Ninja" title="Ninja"><code class="xref cmake cmake-generator docutils literal notranslate">Ninja</code></a> generator, this places the command in
the <code class="docutils literal notranslate">console</code> <a class="reference internal" href="../prop_gbl/JOB_POOLS.html#prop_gbl:JOB_POOLS" title="JOB_POOLS"><code class="xref cmake cmake-prop_gbl docutils literal notranslate">pool</code></a>.
</dd>
<dt><code class="docutils literal notranslate">VERBATIM</code></dt><dd>All arguments to the commands will be escaped properly for the
build tool so that the invoked command receives each argument
unchanged. Note that one level of escapes is still used by the
CMake language processor before add_custom_command even sees the
arguments. Use of <code class="docutils literal notranslate">VERBATIM</code> is recommended as it enables
correct behavior. When <code class="docutils literal notranslate">VERBATIM</code> is not given the behavior
is platform specific because there is no protection of
tool-specific special characters.
</dd>
<dt><code class="docutils literal notranslate">WORKING_DIRECTORY</code></dt><dd>Execute the command with the given current working directory.
If it is a relative path it will be interpreted relative to the
build tree directory corresponding to the current source directory.
<div class="versionadded">
New in version 3.13: Arguments to <code class="docutils literal notranslate">WORKING_DIRECTORY</code> may use
<a class="reference internal" href="../manual/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>.
</div>
</dd>
<dt><code class="docutils literal notranslate">DEPFILE</code></dt><dd><div class="versionadded">
New in version 3.7.
</div>
Specify a depfile which holds dependencies for the custom command. It is
usually emitted by the custom command itself. This keyword may only be used
if the generator supports it, as detailed below.
The expected format, compatible with what is generated by <code class="docutils literal notranslate">gcc</code> with the
option <code class="docutils literal notranslate">-M</code>, is independent of the generator or platform.
The formal syntax, as specified using
<a class="reference external" href="https://en.wikipedia.org/wiki/Backus%E2%80%93Naur_form">BNF</a> notation with
the regular extensions, is the following:
<pre>
depfile ::= <a class="reference internal" href="#grammar-token-depfile-rule"><code class="xref docutils literal notranslate">rule</code></a>*
rule ::= <a class="reference internal" href="#grammar-token-depfile-targets"><code class="xref docutils literal notranslate">targets</code></a> (':' (<a class="reference internal" href="#grammar-token-depfile-separator"><code class="xref docutils literal notranslate">separator</code></a> <a class="reference internal" href="#grammar-token-depfile-dependencies"><code class="xref docutils literal notranslate">dependencies</code></a>?)?)? <a class="reference internal" href="#grammar-token-depfile-eol"><code class="xref docutils literal notranslate">eol</code></a>
targets ::= <a class="reference internal" href="#grammar-token-depfile-target"><code class="xref docutils literal notranslate">target</code></a> (<a class="reference internal" href="#grammar-token-depfile-separator"><code class="xref docutils literal notranslate">separator</code></a> <a class="reference internal" href="#grammar-token-depfile-target"><code class="xref docutils literal notranslate">target</code></a>)* <a class="reference internal" href="#grammar-token-depfile-separator"><code class="xref docutils literal notranslate">separator</code></a>*
target ::= <a class="reference internal" href="#grammar-token-depfile-pathname"><code class="xref docutils literal notranslate">pathname</code></a>
dependencies ::= <a class="reference internal" href="#grammar-token-depfile-dependency"><code class="xref docutils literal notranslate">dependency</code></a> (<a class="reference internal" href="#grammar-token-depfile-separator"><code class="xref docutils literal notranslate">separator</code></a> <a class="reference internal" href="#grammar-token-depfile-dependency"><code class="xref docutils literal notranslate">dependency</code></a>)* <a class="reference internal" href="#grammar-token-depfile-separator"><code class="xref docutils literal notranslate">separator</code></a>*
dependency ::= <a class="reference internal" href="#grammar-token-depfile-pathname"><code class="xref docutils literal notranslate">pathname</code></a>
separator ::= (<a class="reference internal" href="#grammar-token-depfile-space"><code class="xref docutils literal notranslate">space</code></a> | <a class="reference internal" href="#grammar-token-depfile-line_continue"><code class="xref docutils literal notranslate">line_continue</code></a>)+
line_continue ::= '\' <a class="reference internal" href="#grammar-token-depfile-eol"><code class="xref docutils literal notranslate">eol</code></a>
space ::= ' ' | '\t'
pathname ::= <a class="reference internal" href="#grammar-token-depfile-character"><code class="xref docutils literal notranslate">character</code></a>+
character ::= <a class="reference internal" href="#grammar-token-depfile-std_character"><code class="xref docutils literal notranslate">std_character</code></a> | <a class="reference internal" href="#grammar-token-depfile-dollar"><code class="xref docutils literal notranslate">dollar</code></a> | <a class="reference internal" href="#grammar-token-depfile-hash"><code class="xref docutils literal notranslate">hash</code></a> | <a class="reference internal" href="#grammar-token-depfile-whitespace"><code class="xref docutils literal notranslate">whitespace</code></a>
std_character ::= &lt;any character except '$', '#' or ' '&gt;
dollar ::= '$$'
hash ::= '\#'
whitespace ::= '\ '
eol ::= '\r'? '\n'
</pre>
<div class="admonition note">
Note
As part of <code class="docutils literal notranslate">pathname</code>, any slash and backslash is interpreted as
a directory separator.
</div>
<div class="versionadded">
New in version 3.7: The <a class="reference internal" href="../generator/Ninja.html#generator:Ninja" title="Ninja"><code class="xref cmake cmake-generator docutils literal notranslate">Ninja</code></a> generator supports <code class="docutils literal notranslate">DEPFILE</code> since the keyword
was first added.
</div>
<div class="versionadded">
New in version 3.17: Added the <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> generator, which included
support for the <code class="docutils literal notranslate">DEPFILE</code> keyword.
</div>
<div class="versionadded">
New in version 3.20: Added support for <a class="reference internal" href="../manual/cmake-generators.7.html#makefile-generators">Makefile Generators</a>.
<div class="admonition note">
Note
<code class="docutils literal notranslate">DEPFILE</code> cannot be specified at the same time as the
<code class="docutils literal notranslate">IMPLICIT_DEPENDS</code> option for <a class="reference internal" href="../manual/cmake-generators.7.html#makefile-generators">Makefile Generators</a>.
</div>
</div>
<div class="versionadded">
New in version 3.21: Added support for <a class="reference internal" href="../manual/cmake-generators.7.html#visual-studio-generators">Visual Studio Generators</a> with VS 2012 and above,
and for the <a class="reference internal" href="../generator/Xcode.html#generator:Xcode" title="Xcode"><code class="xref cmake cmake-generator docutils literal notranslate">Xcode</code></a> generator. Support for
<a class="reference internal" href="../manual/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> was also
added.
</div>
Using <code class="docutils literal notranslate">DEPFILE</code> with generators other than those listed above is an error.
If the <code class="docutils literal notranslate">DEPFILE</code> argument is relative, it should be relative to
<a class="reference internal" href="../variable/CMAKE_CURRENT_BINARY_DIR.html#variable:CMAKE_CURRENT_BINARY_DIR" title="CMAKE_CURRENT_BINARY_DIR"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_CURRENT_BINARY_DIR</code></a>, and any relative paths inside the
<code class="docutils literal notranslate">DEPFILE</code> should also be relative to <a class="reference internal" href="../variable/CMAKE_CURRENT_BINARY_DIR.html#variable:CMAKE_CURRENT_BINARY_DIR" title="CMAKE_CURRENT_BINARY_DIR"><code class="xref cmake cmake-variable docutils literal notranslate">CMAKE_CURRENT_BINARY_DIR</code></a>.
See policy <a class="reference internal" href="../policy/CMP0116.html#policy:CMP0116" title="CMP0116"><code class="xref cmake cmake-policy docutils literal notranslate">CMP0116</code></a>, which is always <code class="docutils literal notranslate">NEW</code> for
<a class="reference internal" href="../manual/cmake-generators.7.html#makefile-generators">Makefile Generators</a>, <a class="reference internal" href="../manual/cmake-generators.7.html#visual-studio-generators">Visual Studio Generators</a>,
and the <a class="reference internal" href="../generator/Xcode.html#generator:Xcode" title="Xcode"><code class="xref cmake cmake-generator docutils literal notranslate">Xcode</code></a> generator.
</dd>
</dl>
</section>
<section id="examples-generating-files">
<h2>Examples: Generating Files<a class="headerlink" href="#examples-generating-files" title="Permalink to this heading">¶</a></h2>
Custom commands may be used to generate source files.
For example, the code:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_custom_command(
 OUTPUT out.c
 COMMAND someTool -i ${CMAKE_CURRENT_SOURCE_DIR}/in.txt
 -o out.c
 DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/in.txt
 VERBATIM)
add_library(myLib out.c)
</pre></div>
</div>
adds a custom command to run <code class="docutils literal notranslate">someTool</code> to generate <code class="docutils literal notranslate">out.c</code> and then
compile the generated source as part of a library. The generation rule
will re-run whenever <code class="docutils literal notranslate">in.txt</code> changes.
<div class="versionadded">
New in version 3.20: One may use generator expressions to specify per-configuration outputs.
For example, the code:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_custom_command(
 OUTPUT &quot;out-$&lt;CONFIG&gt;.c&quot;
 COMMAND someTool -i ${CMAKE_CURRENT_SOURCE_DIR}/in.txt
 -o &quot;out-$&lt;CONFIG&gt;.c&quot;
 -c &quot;$&lt;CONFIG&gt;&quot;
 DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/in.txt
 VERBATIM)
add_library(myLib &quot;out-$&lt;CONFIG&gt;.c&quot;)
</pre></div>
</div>
adds a custom command to run <code class="docutils literal notranslate">someTool</code> to generate <code class="docutils literal notranslate">out-&lt;config&gt;.c</code>,
where <code class="docutils literal notranslate">&lt;config&gt;</code> is the build configuration, and then compile the generated
source as part of a library.
</div>
<section id="example-generating-files-for-multiple-targets">
<h3>Example: Generating Files for Multiple Targets<a class="headerlink" href="#example-generating-files-for-multiple-targets" title="Permalink to this heading">¶</a></h3>
If multiple independent targets need the same custom command output,
it must be attached to a single custom target on which they all depend.
Consider the following example:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_custom_command(
 OUTPUT table.csv
 COMMAND makeTable -i ${CMAKE_CURRENT_SOURCE_DIR}/input.dat
 -o table.csv
 DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/input.dat
 VERBATIM)
add_custom_target(generate_table_csv DEPENDS table.csv)

add_custom_command(
 OUTPUT bar.cxx
 COMMAND genFromTable -i table.csv -case bar -o bar.cxx
 DEPENDS table.csv # file-level dependency
 generate_table_csv # target-level dependency
 VERBATIM)
add_library(bar bar.cxx)
</pre></div>
</div>
Output <code class="docutils literal notranslate">foo.cxx</code> is needed only by target <code class="docutils literal notranslate">foo</code> and output <code class="docutils literal notranslate">bar.cxx</code>
is needed only by target <code class="docutils literal notranslate">bar</code>, but both targets need <code class="docutils literal notranslate">table.csv</code>,
transitively. Since <code class="docutils literal notranslate">foo</code> and <code class="docutils literal notranslate">bar</code> are independent targets that may
build concurrently, we prevent them from racing to generate <code class="docutils literal notranslate">table.csv</code>
by placing its custom command in a separate target, <code class="docutils literal notranslate">generate_table_csv</code>.
The custom commands generating <code class="docutils literal notranslate">foo.cxx</code> and <code class="docutils literal notranslate">bar.cxx</code> each specify a
target-level dependency on <code class="docutils literal notranslate">generate_table_csv</code>, so the targets using them,
<code class="docutils literal notranslate">foo</code> and <code class="docutils literal notranslate">bar</code>, will not build until after target <code class="docutils literal notranslate">generate_table_csv</code>
is built.
</section>
</section>
<section id="build-events">
<h2>Build Events<a class="headerlink" href="#build-events" title="Permalink to this heading">¶</a></h2>
The second signature adds a custom command to a target such as a
library or executable. This is useful for performing an operation
before or after building the target. The command becomes part of the
target and will only execute when the target itself is built. If the
target is already built, the command will not execute.
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_custom_command(TARGET &lt;target&gt;
 PRE_BUILD | PRE_LINK | POST_BUILD
 COMMAND command1 [ARGS] [args1...]
 [COMMAND command2 [ARGS] [args2...] ...]
 [BYPRODUCTS [files...]]
 [WORKING_DIRECTORY dir]
 [COMMENT comment]
 [VERBATIM] [USES_TERMINAL]
 [COMMAND_EXPAND_LISTS])
</pre></div>
</div>
This defines a new command that will be associated with building the
specified <code class="docutils literal notranslate">&lt;target&gt;</code>. The <code class="docutils literal notranslate">&lt;target&gt;</code> must be defined in the current
directory; targets defined in other directories may not be specified.
When the command will happen is determined by which
of the following is specified:
<dl class="simple">
<dt><code class="docutils literal notranslate">PRE_BUILD</code></dt><dd>On <a class="reference internal" href="../manual/cmake-generators.7.html#visual-studio-generators">Visual Studio Generators</a>, run before any other rules are
executed within the target.
On other generators, run just before <code class="docutils literal notranslate">PRE_LINK</code> commands.
</dd>
<dt><code class="docutils literal notranslate">PRE_LINK</code></dt><dd>Run after sources have been compiled but before linking the binary
or running the librarian or archiver tool of a static library.
This is not defined for targets created by the
<a class="reference internal" href="add_custom_target.html#command:add_custom_target" title="add_custom_target"><code class="xref cmake cmake-command docutils literal notranslate">add_custom_target()</code></a> command.
</dd>
<dt><code class="docutils literal notranslate">POST_BUILD</code></dt><dd>Run after all other rules within the target have been executed.
</dd>
</dl>
Projects should always specify one of the above three keywords when using
the <code class="docutils literal notranslate">TARGET</code> form. For backward compatibility reasons, <code class="docutils literal notranslate">POST_BUILD</code> is
assumed if no such keyword is given, but projects should explicitly provide
one of the keywords to make clear the behavior they expect.
<div class="admonition note">
Note
Because generator expressions can be used in custom commands,
it is possible to define <code class="docutils literal notranslate">COMMAND</code> lines or whole custom commands
which evaluate to empty strings for certain configurations.
For Visual Studio 11 2012 (and newer) generators these command
lines or custom commands will be omitted for the specific
configuration and no &quot;empty-string-command&quot; will be added.
This allows to add individual build events for every configuration.
</div>
<div class="versionadded">
New in version 3.21: Support for target-dependent generator expressions.
</div>
</section>
<section id="examples-build-events">
<h2>Examples: Build Events<a class="headerlink" href="#examples-build-events" title="Permalink to this heading">¶</a></h2>
A <code class="docutils literal notranslate">POST_BUILD</code> event may be used to post-process a binary after linking.
For example, the code:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_executable(myExe myExe.c)
add_custom_command(
 TARGET myExe POST_BUILD
 COMMAND someHasher -i &quot;$&lt;TARGET_FILE:myExe&gt;&quot;
 -o &quot;$&lt;TARGET_FILE:myExe&gt;.hash&quot;
 VERBATIM)
</pre></div>
</div>
will run <code class="docutils literal notranslate">someHasher</code> to produce a <code class="docutils literal notranslate">.hash</code> file next to the executable
after linking.
<div class="versionadded">
New in version 3.20: One may use generator expressions to specify per-configuration byproducts.
For example, the code:
<div class="highlight-cmake notranslate"><div class="highlight"><pre>add_library(myPlugin MODULE myPlugin.c)
add_custom_command(
 TARGET myPlugin POST_BUILD
 COMMAND someHasher -i &quot;$&lt;TARGET_FILE:myPlugin&gt;&quot;
 --as-code &quot;myPlugin-hash-$&lt;CONFIG&gt;.c&quot;
 BYPRODUCTS &quot;myPlugin-hash-$&lt;CONFIG&gt;.c&quot;
 VERBATIM)
add_executable(myExe myExe.c &quot;myPlugin-hash-$&lt;CONFIG&gt;.c&quot;)
</pre></div>
</div>
will run <code class="docutils literal notranslate">someHasher</code> after linking <code class="docutils literal notranslate">myPlugin</code>, e.g. to produce a <code class="docutils literal notranslate">.c</code>
file containing code to check the hash of <code class="docutils literal notranslate">myPlugin</code> that the <code class="docutils literal notranslate">myExe</code>
executable can use to verify it before loading.
</div>
</section>
<section id="ninja-multi-config">
<h2>Ninja Multi-Config<a class="headerlink" href="#ninja-multi-config" title="Permalink to this heading">¶</a></h2>
<div class="versionadded">
New in version 3.20: <code class="docutils literal notranslate">add_custom_command</code> supports the <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>
generator's cross-config capabilities. See the generator documentation
for more information.
</div>
</section>
<section id="see-also">
<h2>See Also<a class="headerlink" href="#see-also" title="Permalink to this heading">¶</a></h2>
<ul class="simple">
<li><a class="reference internal" href="add_custom_target.html#command:add_custom_target" title="add_custom_target"><code class="xref cmake cmake-command docutils literal notranslate">add_custom_target()</code></a></li>
</ul>
</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="#">add_custom_command</a><ul>
<li><a class="reference internal" href="#generating-files">Generating Files</a></li>
<li><a class="reference internal" href="#examples-generating-files">Examples: Generating Files</a><ul>
<li><a class="reference internal" href="#example-generating-files-for-multiple-targets">Example: Generating Files for Multiple Targets</a></li>
</ul>
</li>
<li><a class="reference internal" href="#build-events">Build Events</a></li>
<li><a class="reference internal" href="#examples-build-events">Examples: Build Events</a></li>
<li><a class="reference internal" href="#ninja-multi-config">Ninja Multi-Config</a></li>
<li><a class="reference internal" href="#see-also">See Also</a></li>
</ul>
</li>
</ul>

</div>
 <div>
 <h4>Previous topic</h4>
 <a href="add_compile_options.html"
 title="previous chapter">add_compile_options</a>
 </div>
 <div>
 <h4>Next topic</h4>
 <a href="add_custom_target.html"
 title="next chapter">add_custom_target</a>
 </div>
 <div role="note" aria-label="source link">
 <h3>This Page</h3>
 <ul class="this-page-menu">
 <li><a href="../_sources/command/add_custom_command.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="add_custom_target.html" title="add_custom_target"
 >next</a> |</li>
 <li class="right" >
 <a href="add_compile_options.html" title="add_compile_options"
 >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-1"><a href="../manual/cmake-commands.7.html" >cmake-commands(7)</a> &#187;</li>
 <li class="nav-item nav-item-this"><a href="">add_custom_command</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>