Searched +refs:cmake +refs:command +refs:run (Results 1 – 25 of 136) sorted by relevance
123456
| /prebuilts/cmake/linux-x86/share/cmake-3.22/Help/command/ |
| D | add_custom_command.rst | 11 The first signature is for adding a custom command to produce an output:
13 .. code-block:: cmake
30 This defines a command to generate specified ``OUTPUT`` file(s).
32 that specifies any output of the custom command as a source file
33 is given a rule to generate the file using the command at build time.
36 (instead use the :command:`add_custom_target` command to drive the
37 command and make the other targets depend on that one).
47 command for the first output specified. There must have already
48 been a previous call to this command with the same output.
62 Specify the files the command is expected to produce but whose
[all …]
|
| D | add_test.rst | 4 Add a test to the project to be run by :manual:`ctest(1)`.
6 .. code-block:: cmake
8 add_test(NAME <name> COMMAND <command> [<arg>...]
18 Specify the test command-line. If ``<command>`` specifies an
19 executable target (created by :command:`add_executable`) it will
29 If not specified the test will be run with the current working
38 :manual:`generator expressions <cmake-generator-expressions(7)>`.
40 The given test command is expected to exit with code ``0`` to pass and
53 :manual:`cmake-generator-expressions(7)` manual for available expressions.
57 .. code-block:: cmake
[all …]
|
| D | try_run.rst | 13 .. code-block:: cmake
29 executable was built, but failed to run, then ``<runResultVar>`` will be
30 set to ``FAILED_TO_RUN``. See the :command:`try_compile` command for
42 the ``cmake`` command-line used to drive the test build.
43 The example in :command:`try_compile` shows how values for variables
48 Specify ``-Ddefinition`` arguments to pass to :command:`add_definitions`
67 Specify link step options to pass to :command:`target_link_options` in the
82 specified, the executable will run in ``<bindir>``.
98 usually cannot be run on the build host. The ``try_run`` command checks
101 the executable, but it will not try to run the executable unless the
[all …]
|
| D | install.rst | 4 Specify rules to run at install time.
23 This command generates installation rules for a project. Install rules
24 specified by calls to the ``install()`` command within a source directory
29 added by calls to the :command:`add_subdirectory` command are interleaved
30 with those in the parent directory to run in the order declared (see
35 default copying behavior of :command:`install()`.
37 There are multiple signatures for this command. Some of them define
75 .. code-block:: cmake
105 installed by the command.
130 .. code-block:: cmake
[all …]
|
| D | add_custom_target.rst | 6 .. code-block:: cmake
22 Use the :command:`add_custom_command` command to generate a file with
24 the :command:`add_dependencies` command to add dependencies to or
31 target so that it will be run every time (the command cannot be
37 Specify the files the command is expected to produce but whose
59 :manual:`generator expressions <cmake-generator-expressions(7)>`.
64 Specify the command-line(s) to execute at build time.
67 (To run a full script, use the :command:`configure_file` command or the
68 :command:`file(GENERATE)` command to create it, and then specify
72 :command:`add_executable` command), it will automatically be replaced
[all …]
|
| D | exec_program.rst | 6 Use the :command:`execute_process` command instead.
13 exec_program(Executable [directory in which to run]
18 The executable is run in the optionally specified directory. The
21 program. This is because cmake will then be able to escape spaces in
26 running cmake.
|
| D | try_compile.rst | 13 .. code-block:: cmake
28 will not be deleted after this command is run. Specify ``<targetName>`` to
35 .. code-block:: cmake
67 .. code-block:: cmake
80 the ``cmake`` command-line used to drive the test build.
86 Specify ``-Ddefinition`` arguments to pass to :command:`add_definitions`
107 Specify link step options to pass to :command:`target_link_options` or to
138 passed to ``cmake`` to avoid this clean. However, multiple sequential
142 project by ``if(NOT DEFINED <resultVar>)`` logic, configure with cmake
144 the try_compile call of interest, and then re-run cmake again with
[all …]
|
| /prebuilts/cmake/linux-x86/share/cmake-3.22/Help/manual/ |
| D | cmake.1.rst | 1 .. cmake-manual-description: CMake Command-Line Reference
3 cmake(1)
12 cmake [<options>] <path-to-source>
13 cmake [<options>] <path-to-existing-build>
14 cmake [<options>] -S <path-to-source> -B <path-to-build>
17 cmake --build <dir> [<options>] [-- <build-tool-options>]
20 cmake --install <dir> [<options>]
23 cmake --open <dir>
26 cmake [{-D <var>=<value>}...] -P <cmake-script-file>
29 cmake -E <command> [<options>]
[all …]
|
| D | cmake-qt.7.rst | 1 .. cmake-manual-description: CMake Qt Features Reference
3 cmake-qt(7)
16 :manual:`cmake-packages(7)` for more information about CMake packages, and
17 see `the Qt cmake manual <http://qt-project.org/doc/qt-5/cmake-manual.html>`_
21 :manual:`CMake buildsystem <cmake-buildsystem(7)>`:
23 .. code-block:: cmake
48 automatically invoked by :manual:`cmake(1)` if the appropriate conditions
56 The :prop_tgt:`AUTOMOC` target property controls whether :manual:`cmake(1)`
58 be run, and to create rules to execute ``moc`` at the appropriate time.
61 ``moc`` will be run on the file. The result will be put into a file named
[all …]
|
| /prebuilts/cmake/linux-x86/share/cmake-3.22/Help/generator/ |
| D | Ninja Multi-Config.rst | 17 are intended to be run with ``ninja -f build-<Config>.ninja``. A
22 ``cmake --build . --config <Config>`` will always use ``build-<Config>.ninja``
23 to build. If no ``--config`` argument is specified, ``cmake --build .`` will
55 .. code-block:: cmake
64 Now assume you configure the project with ``Ninja Multi-Config`` and run one of
71 cmake --build . --config Debug --target generated
77 But if :variable:`CMAKE_CROSS_CONFIGS` is set to ``all``, and you run the
84 cmake --build . --config Release --target generated:Debug
98 :command:`add_custom_command` and :command:`add_custom_target` through its
100 arguments can be evaluated in the context of either the "command config" (the
[all …]
|
| /prebuilts/cmake/linux-x86/share/cmake-3.22/Modules/ |
| D | CheckFortranSourceRuns.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details.
11 subsequently be run.
13 .. command:: check_fortran_source_runs
15 .. code-block:: cmake
21 file, linked as an executable and then run. The ``<code>`` must be a Fortran program
24 .. code-block:: cmake
28 This command can help avoid costly build processes when a compiler lacks support
34 If the ``<code>`` could be built and run
42 The underlying check is performed by the :command:`try_run` command. The
50 command before the contents of ``CMAKE_REQUIRED_FLAGS``.
[all …]
|
| D | CheckOBJCXXSourceRuns.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details.
11 subsequently be run.
13 .. command:: check_objcxx_source_runs
15 .. code-block:: cmake
20 file, linked as an executable and then run. The ``<code>`` must contain at
21 least a ``main()`` function. If the ``<code>`` could be built and run
26 The underlying check is performed by the :command:`try_run` command. The
34 command before the contents of ``CMAKE_REQUIRED_FLAGS``.
49 command (see :command:`try_run` for further details).
53 command. These can be the name of system libraries or they can be
[all …]
|
| D | CheckOBJCSourceRuns.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details.
11 subsequently be run.
13 .. command:: check_objc_source_runs
15 .. code-block:: cmake
20 file, linked as an executable and then run. The ``<code>`` must contain at
21 least a ``main()`` function. If the ``<code>`` could be built and run
26 The underlying check is performed by the :command:`try_run` command. The
34 command before the contents of ``CMAKE_REQUIRED_FLAGS``.
49 command (see :command:`try_run` for further details).
53 command. These can be the name of system libraries or they can be
[all …]
|
| D | CheckCXXSourceRuns.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details.
9 subsequently be run.
11 .. command:: check_cxx_source_runs
13 .. code-block:: cmake
18 file, linked as an executable and then run. The ``<code>`` must contain at
19 least a ``main()`` function. If the ``<code>`` could be built and run
24 The underlying check is performed by the :command:`try_run` command. The
32 command before the contents of ``CMAKE_REQUIRED_FLAGS``.
49 command (see :command:`try_run` for further details).
53 command. These can be the name of system libraries or they can be
[all …]
|
| D | CheckCSourceRuns.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details.
9 subsequently be run.
11 .. command:: check_c_source_runs
13 .. code-block:: cmake
18 file, linked as an executable and then run. The ``<code>`` must contain at
19 least a ``main()`` function. If the ``<code>`` could be built and run
24 The underlying check is performed by the :command:`try_run` command. The
32 command before the contents of ``CMAKE_REQUIRED_FLAGS``.
49 command (see :command:`try_run` for further details).
53 command. These can be the name of system libraries or they can be
[all …]
|
| D | CheckSourceRuns.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details.
12 subsequently be run.
14 .. command:: check_source_runs
16 .. code-block:: cmake
22 file for the requested language, linked as an executable and then run.
24 could be built and run successfully, the internal cache variable specified by
32 The underlying check is performed by the :command:`try_run` command. The
40 command before the contents of ``CMAKE_REQUIRED_FLAGS``.
55 command (see :command:`try_run` for further details).
59 command. These can be the name of system libraries or they can be
[all …]
|
| D | GoogleTest.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details.
11 mechanisms for adding tests are provided. :command:`gtest_add_tests` has been
13 :command:`gtest_discover_tests` was introduced in CMake 3.10.
15 The (older) :command:`gtest_add_tests` scans source files to identify tests.
21 The (newer) :command:`gtest_discover_tests` discovers tests by asking the
24 to be re-run when tests change. However, it may not work in a cross-compiling
29 Both commands are intended to replace use of :command:`add_test` to register
38 .. command:: gtest_add_tests
57 re-run to discover any newly added, removed or renamed tests (by default,
58 this means that CMake is re-run when any test source file is changed, but see
[all …]
|
| D | ExternalProject.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details.
20 .. command:: ExternalProject_Add
26 .. code-block:: cmake
43 :command:`ExternalProject_Get_Property` command to retrieve their values,
131 Overrides the command used for the download step
132 (:manual:`generator expressions <cmake-generator-expressions(7)>` are
143 :command:`file(DOWNLOAD)` command. A local filesystem path may refer to
157 algorithms supported by the :command:`file()` command. Specifying this
182 :command:`ExternalProject_Get_Property` command.
216 :command:`file(DOWNLOAD)`). If that is also not set, certificate
[all …]
|
| D | FindGit.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details.
11 Path to Git command-line client.
13 True if the Git command-line client was found.
22 Executable of the Git command-line client.
26 .. code-block:: cmake
58 DOC "Git command line client"
64 # command prompt happens to have a PATH entry with a Git/ subdirectory
70 DOC "Git command line client"
80 # Avoid querying the version if we've already done that this run. For
86 # between CMake runs, but it shouldn't change during a run for a given
[all …]
|
| D | CheckFortranSourceCompiles.cmake | 2 # file Copyright.txt or https://cmake.org/licensing for details.
12 .. command:: check_fortran_source_compiles
14 .. code-block:: cmake
25 .. code-block:: cmake
29 This command can help avoid costly build processes when a compiler lacks support
33 :command:`check_fortran_source_runs` command to actually run the compiled code.
46 The underlying check is performed by the :command:`try_compile` command. The
54 command before the contents of ``CMAKE_REQUIRED_FLAGS``.
71 command (see :command:`try_compile` for further details).
75 command. These can be the name of system libraries or they can be
[all …]
|
| /prebuilts/cmake/linux-x86/share/cmake-3.22/Help/release/ |
| D | 3.17.rst | 16 * :manual:`cmake(1)` gained a :generator:`Ninja Multi-Config` generator,
35 * The :manual:`Compile Features <cmake-compile-features(7)>` functionality
49 * :manual:`cmake(1)` gained a ``--debug-find`` command-line option to
52 * :manual:`cmake(1)` gained a ``--trace-format`` command-line option that
57 * :manual:`cmake(1)` gained a ``-E rm`` command-line tool that can be
64 * The :command:`add_custom_command` command learned to interpret paths in
68 * The :command:`foreach` command learned a new ``ZIP_LISTS`` option to iterate
71 * The :command:`load_cache(READ_WITH_PREFIX)` command mode is now allowed
72 when using ``cmake -P`` to :ref:`Run a Script <Script Processing Mode>`.
74 * The :command:`message` command learned to output context provided in
[all …]
|
| D | 3.21.rst | 16 * :manual:`cmake-presets(7)` gained support for specifying the install prefix
19 * :manual:`cmake-presets(7)` gained support for conditional enabling of presets.
21 * :manual:`cmake-presets(7)` gained support for a ``${hostSystemName}`` macro.
23 * :manual:`cmake-presets(7)` gained support for omitting the ``generator`` and
41 enabled via the :command:`project` and :command:`enable_language` commands.
44 :manual:`Compile Features <cmake-compile-features(7)>` functionality gained
52 * :manual:`cmake(1)` gained the ``--install-prefix <dir>``
53 command-line option to specify the location of the install prefix.
55 * :manual:`cmake(1)` gained the ``--toolchain <path/to/file>``
56 command-line option to specify a toolchain file.
[all …]
|
| D | 3.7.rst | 52 * The :command:`add_custom_command` command gained a new ``DEPFILE``
56 * The :command:`cmake_parse_arguments` command gained a new ``PARSE_ARGV``
58 variables inside a :command:`function` body.
60 * The :command:`export` command gained an ``ANDROID_MK`` option
64 * The :command:`file(DOWNLOAD)` and :command:`file(UPLOAD)` commands gained
67 * The :command:`find_library` and :command:`find_package` commands learned
72 * The :command:`find_package` command gained the possibility of
77 * The :command:`if` command gained new boolean comparison operations
81 * The :command:`install` command gained an ``EXPORT_ANDROID_MK``
85 * The :command:`string(TIMESTAMP)` and :command:`file(TIMESTAMP)`
[all …]
|
| D | 3.15.rst | 22 * It now supports the :command:`add_custom_command` and
23 :command:`add_custom_target` commands.
52 but has a GNU-like command line is now supported.
66 to specify a default generator to use when :manual:`cmake(1)` is
67 run without a ``-G`` option. Additionally, environment variables
72 * The :manual:`cmake(1)` ``--build`` tool ``--target`` parameter gained support
73 for multiple targets, e.g. ``cmake --build . --target Library1 Library2``.
75 ``cmake --build . -t Library1 Library2``.
77 * The :manual:`cmake(1)` command gained a new ``--install`` option.
78 This may be used after building a project to run installation without
[all …]
|
| D | 3.0.rst | 23 ``cmake --help-command`` and similar command-line options.
27 - :manual:`cmake-buildsystem(7)`
28 - :manual:`cmake-commands(7)`, replacing ``cmakecommands(1)``
30 - :manual:`cmake-developer(7)`
31 - :manual:`cmake-generator-expressions(7)`
32 - :manual:`cmake-generators(7)`
33 - :manual:`cmake-language(7)`
34 - :manual:`cmake-modules(7)`, replacing ``cmakemodules(1)``
35 - :manual:`cmake-packages(7)`
36 - :manual:`cmake-policies(7)`, replacing ``cmakepolicies(1)``
[all …]
|
123456