Searched +refs:cmake +refs:command +refs:run (Results 1 – 25 of 468) sorted by relevance
12345678910>>...19
3 To build libwebm you must first create project files. To do this run cmake6 Makefile.unix can be used as a fallback on systems that cmake does not13 run cmake with the path to the libwebm repo:15 $ cmake path/to/libwebm17 On Windows the above command will produce Visual Studio project files for the19 above command will produce a makefile.22 the cmake command line. This argument must be followed by the name of a23 generator. Running cmake with the --help argument will list the available26 On Mac OS X you would run the following command to generate Xcode projects:28 $ cmake path/to/libwebm -G Xcode[all …]
3 …ork operators for ARM and x86 CPU platforms. Our delegate lowers models to run using these highly …20 The following command will produce a floating-point XNNPACK delegated model `mv2_xnnpack_fp32.pte` …27 …(pte) file, then let's run it with ExecuTorch runtime using the `xnn_executor_runner`. With cmake,…33 # Get a clean cmake-out directory34 rm -rf cmake-out35 mkdir cmake-out37 # Configure cmake38 cmake \39 -DCMAKE_INSTALL_PREFIX=cmake-out \53 cmake --build cmake-out -j9 --target install --config Release[all …]
1 .. cmake-manual-description: CMake Command-Line Reference3 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 …]
1 .. cmake-manual-description: CMake Qt Features Reference3 cmake-qt(7)16 :manual:`cmake-packages(7)` for more information about CMake packages, and17 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:: cmake48 automatically invoked by :manual:`cmake(1)` if the appropriate conditions56 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 …]
11 The first signature is for adding a custom command to produce an output:13 .. code-block:: cmake30 This defines a command to generate specified ``OUTPUT`` file(s).32 that specifies any output of the custom command as a source file33 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 the37 command and make the other targets depend on that one).47 command for the first output specified. There must have already48 been a previous call to this command with the same output.62 Specify the files the command is expected to produce but whose[all …]
4 Add a test to the project to be run by :manual:`ctest(1)`.6 .. code-block:: cmake8 add_test(NAME <name> COMMAND <command> [<arg>...]18 Specify the test command-line. If ``<command>`` specifies an19 executable target (created by :command:`add_executable`) it will29 If not specified the test will be run with the current working38 :manual:`generator expressions <cmake-generator-expressions(7)>`.40 The given test command is expected to exit with code ``0`` to pass and53 :manual:`cmake-generator-expressions(7)` manual for available expressions.57 .. code-block:: cmake[all …]
4 Specify rules to run at install time.23 This command generates installation rules for a project. Install rules24 specified by calls to the ``install()`` command within a source directory29 added by calls to the :command:`add_subdirectory` command are interleaved30 with those in the parent directory to run in the order declared (see35 default copying behavior of :command:`install()`.37 There are multiple signatures for this command. Some of them define75 .. code-block:: cmake105 installed by the command.130 .. code-block:: cmake[all …]
4 [CMake](https://cmake.org/) tool.14 It requires CMake 3.16 or higher. On Ubuntu, you can simply run the following15 command.18 sudo apt-get install cmake22 [the official cmake installation guide](https://cmake.org/install/)45 your workstation, simply run the following command.48 cmake ../tensorflow_src/tensorflow/lite57 cmake ../tensorflow_src/tensorflow/lite -DCMAKE_BUILD_TYPE=Debug62 In order to be able to run kernel tests, you need to provide67 cmake ../tensorflow_src/tensorflow/lite -DTFLITE_KERNEL_TEST=on[all …]
17 are intended to be run with ``ninja -f build-<Config>.ninja``. A22 ``cmake --build . --config <Config>`` will always use ``build-<Config>.ninja``23 to build. If no ``--config`` argument is specified, ``cmake --build .`` will55 .. code-block:: cmake64 Now assume you configure the project with ``Ninja Multi-Config`` and run one of71 cmake --build . --config Debug --target generated77 But if :variable:`CMAKE_CROSS_CONFIGS` is set to ``all``, and you run the84 cmake --build . --config Release --target generated:Debug98 :command:`add_custom_command` and :command:`add_custom_target` through its100 arguments can be evaluated in the context of either the "command config" (the[all …]
31 - [Running tests via CMake](#running-the-tests-via-the-cmake-build)50 1. [CMake](https://cmake.org). See CMakeLists.txt for the minimum version60 present, yasm will be used by default. Pass -DENABLE_NASM=ON to cmake to76 # By default, the above command stores the source in the aom directory:88 $ cmake path/to/aom96 run the generated build will use cc and c++ by default.106 Both types of options are set at the time CMake is run. The following example110 $ cmake path/to/aom -DENABLE_CCACHE=1 -DCONFIG_AV1_ENCODER=0117 currently be found in the file `build/cmake/aom_config_defaults.cmake`.125 $ cmake path/to/aom -DBUILD_SHARED_LIBS=1[all …]
46 some other suitable source if you intend to run Vulkan applications.76 directory and pass it on the CMake command line for building this repository,87 file. Ensure that the `update_glslang_sources.py` script has been run as part89 and pass it on the CMake command line for building this repository, as100 Vulkan-ValidationLayers repository and run:114 so a loader is needed only if the tests are built and run.123 it on the CMake command line for building this repository, as described below.125 If you do not intend to run the tests, you do not need a Vulkan loader.154 cmake -C helper.cmake ..155 cmake --build .[all …]
6 <https://www.cmake.org/>.18 …m/google/googletest/blob/master/googletest/README.md#incorporating-into-an-existing-cmake-project>)30 3. You can then use the CMake command31 [`add_subdirectory()`](https://cmake.org/cmake/help/latest/command/add_subdirectory.html)35 [`target_link_libraries()`](https://cmake.org/cmake/help/latest/command/target_link_libraries.html)39 ```cmake55 …_RUN_TESTS=ON` flag to run Abseil tests. Note that if the `-DBUILD_TESTING=OFF` flag is passed th…64 https://github.com/google/googletest/blob/master/googletest/README.md#using-cmake67 For example, to run just the Abseil tests, you could use this script:73 cmake -DABSL_USE_GOOGLETEST_HEAD=ON -DABSL_RUN_TESTS=ON ..[all …]
236 import setuptools.command.build_ext237 import setuptools.command.install238 import setuptools.command.sdist243 from tools.setup_helpers.cmake import CMake357 cmake = CMake() variable479 cmake=cmake,532 class build_ext(setuptools.command.build_ext.build_ext):598 def run(self): member in build_ext601 cmake_cache_vars = defaultdict(lambda: False, cmake.get_cmake_cache_variables())687 setuptools.command.build_ext.build_ext.run(self)[all …]
11 - [CMake](http://www.cmake.org) v2.8.12 or later54 or later), which includes command-line versions of the 32-bit and 64-bit56 * If you intend to build libjpeg-turbo from the command line, then add the63 * The libjpeg API DLL (**jpeg{version}.dll**) will depend on the C run-time72 Start Menu link that can be used to launch a command prompt with the114 NOTE: The build procedures below assume that CMake is invoked from the command126 cmake -G"Unix Makefiles" [additional CMake flags] {source_directory}169 cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release [additional CMake flags] {source_directory}202 (run `cmake` with no arguments for a list of available generators.) For206 cmake -G"Visual Studio 10" [additional CMake flags] {source_directory}[all …]
16 * :manual:`cmake(1)` gained a :generator:`Ninja Multi-Config` generator,35 * The :manual:`Compile Features <cmake-compile-features(7)>` functionality49 * :manual:`cmake(1)` gained a ``--debug-find`` command-line option to52 * :manual:`cmake(1)` gained a ``--trace-format`` command-line option that57 * :manual:`cmake(1)` gained a ``-E rm`` command-line tool that can be64 * The :command:`add_custom_command` command learned to interpret paths in68 * The :command:`foreach` command learned a new ``ZIP_LISTS`` option to iterate71 * The :command:`load_cache(READ_WITH_PREFIX)` command mode is now allowed72 when using ``cmake -P`` to :ref:`Run a Script <Script Processing Mode>`.74 * The :command:`message` command learned to output context provided in[all …]
16 * :manual:`cmake-presets(7)` gained support for specifying the install prefix19 * :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`` and41 enabled via the :command:`project` and :command:`enable_language` commands.44 :manual:`Compile Features <cmake-compile-features(7)>` functionality gained52 * :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 …]
1 # run-and-compare.cmake -- Runs a command and compares its output to an expected value7 # COMMAND - Command to run24 # Run command with stdin input and redirect stdout to output30 -P ${CMAKE_CURRENT_LIST_DIR}/run-and-redirect.cmake33 # Run command and redirect stdout to output38 -P ${CMAKE_CURRENT_LIST_DIR}/run-and-redirect.cmake
2 # file Copyright.txt or https://cmake.org/licensing for details.20 .. command:: ExternalProject_Add26 .. code-block:: cmake43 :command:`ExternalProject_Get_Property` command to retrieve their values,131 Overrides the command used for the download step132 (:manual:`generator expressions <cmake-generator-expressions(7)>` are143 :command:`file(DOWNLOAD)` command. A local filesystem path may refer to157 algorithms supported by the :command:`file()` command. Specifying this182 :command:`ExternalProject_Get_Property` command.216 :command:`file(DOWNLOAD)`). If that is also not set, certificate[all …]
2 # file Copyright.txt or https://cmake.org/licensing for details.11 subsequently be run.13 .. command:: check_fortran_source_runs15 .. code-block:: cmake21 file, linked as an executable and then run. The ``<code>`` must be a Fortran program24 .. code-block:: cmake28 This command can help avoid costly build processes when a compiler lacks support34 If the ``<code>`` could be built and run42 The underlying check is performed by the :command:`try_run` command. The50 command before the contents of ``CMAKE_REQUIRED_FLAGS``.[all …]
2 # file Copyright.txt or https://cmake.org/licensing for details.11 mechanisms for adding tests are provided. :command:`gtest_add_tests` has been13 :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 the24 to be re-run when tests change. However, it may not work in a cross-compiling29 Both commands are intended to replace use of :command:`add_test` to register38 .. command:: gtest_add_tests57 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 …]
5 You need to have [CMake](http://www.cmake.org), [Visual Studio](https://www.visualstudio.com)31 If *cmake* command is not available from *Command Prompt*, add it to system *PATH* variable:35 If *git* command is not available from *Command Prompt*, add it to system *PATH* variable:83 [generators](http://www.cmake.org/cmake/help/latest/manual/cmake-generators.7.html)88 * [Makefile](http://www.cmake.org/cmake/help/latest/manual/cmake-generators.7.html#makefile-generat…91 * [Visual Studio](http://www.cmake.org/cmake/help/latest/manual/cmake-generators.7.html#visual-stud…94 * [Ninja](https://cmake.org/cmake/help/latest/manual/cmake-generators.7.html#ninja-generator)98 …directly CMake-based projects](https://docs.microsoft.com/en-us/cpp/build/cmake-projects-in-visual…114 C:\Path\to\build\protobuf\release>cmake -G "NMake Makefiles" ^124 C:\Path\to\build\protobuf\debug>cmake -G "Ninja" ^[all …]
52 It is a command-line tool; a GUI tool, Chocolatey GUI, is provided as a53 Chocolatey package, which can be installed from the command line:59 For convenience, the `choco install` command can be run with the `-y`80 downloaded from [here](https://cmake.org/download/).82 When you run the installer, you should choose to add CMake to the system85 CMake can also be installed as the Chocolatey package `cmake`:88 choco install -y cmake94 [here](https://devblogs.microsoft.com/cppblog/cmake-support-in-visual-studio/).114 Visual Studio will run CMake; however, you will need to indicate where135 Visual Studio will then re-run CMake. If that completes without errors,[all …]
61 It is a command-line tool; a GUI tool, Chocolatey GUI, is provided as a62 Chocolatey package, which can be installed from the command line:66 For convenience, the "choco install" command can be run with the "-y"87 https://cmake.org/download/89 When you run the installer, you should choose to add CMake to the system92 CMake can also be installed as the Chocolatey package "cmake":94 choco install -y cmake100 https://devblogs.microsoft.com/cppblog/cmake-support-in-visual-studio/133 Visual Studio will run CMake; however, you will need to indicate where152 Visual Studio will then re-run CMake. If that completes without errors,[all …]
12 command = [ qkey16 'run',25 'run',27 '--dry-run={{DRYRUN}}',43 command = [ qkey47 'run',56 'run',58 '--dry-run={{DRYRUN}}',81 command = [ qkey85 'run',[all …]