Lines Matching +refs:cmake +refs:command +refs:run
31 - [Running tests via CMake](#running-the-tests-via-the-cmake-build)
50 1. [CMake](https://cmake.org). See CMakeLists.txt for the minimum version
60 present, yasm will be used by default. Pass -DENABLE_NASM=ON to cmake to
76 # By default, the above command stores the source in the aom directory:
88 $ cmake path/to/aom
96 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 example
110 $ cmake path/to/aom -DENABLE_CCACHE=1 -DCONFIG_AV1_ENCODER=0
117 currently be found in the file `build/cmake/aom_config_defaults.cmake`.
125 $ cmake path/to/aom -DBUILD_SHARED_LIBS=1
138 $ cmake path/to/aom -DCMAKE_BUILD_TYPE=Debug
146 $ cmake path/to/aom -G Xcode -DCMAKE_CONFIGURATION_TYPES=Debug
157 $ cmake path/to/aom -DAOM_TARGET_CPU=generic
168 - arm64-ios.cmake
169 - arm64-linux-clang.cmake
170 - arm64-linux-gcc.cmake
171 - arm64-mingw-gcc.cmake
172 - armv7-ios.cmake
173 - armv7-linux-gcc.cmake
174 - armv7-mingw-gcc.cmake
175 - armv7s-ios.cmake
176 - ppc-linux-gcc.cmake
177 - riscv-linux-gcc.cmake
178 - x86-ios-simulator.cmake
179 - x86-linux.cmake
180 - x86-macos.cmake
181 - x86-mingw-gcc.cmake
182 - x86\_64-ios-simulator.cmake
183 - x86\_64-mingw-gcc.cmake
185 The following example demonstrates use of the x86-macos.cmake toolchain file on
189 $ cmake path/to/aom \
190 -DCMAKE_TOOLCHAIN_FILE=path/to/aom/build/cmake/toolchains/x86-macos.cmake
203 $ cmake path/to/aom -DAOM_TARGET_CPU=generic
214 sanitizer, add `-DSANITIZE=<type>` to the CMake command line. For example, to
218 $ cmake path/to/aom -DSANITIZE=address
236 $ cmake path/to/aom -G "Visual Studio 17 2022"
239 $ cmake path/to/aom -G "Visual Studio 17 2022" -A Win32
242 $ cmake path/to/aom -G "Visual Studio 16 2019"
245 $ cmake path/to/aom -G "Visual Studio 16 2019" -A Win32
248 $ cmake --build .
260 $ cmake path/to/aom -G Xcode
279 $ cmake path/to/aom \
289 -DCMAKE_TOOLCHAIN_FILE=path/to/emsdk-portable/.../Emscripten.cmake
292 3. Build it: run make if that's your generator of choice:
302 # executed cmake.
319 $ cmake path/to/aom \
332 $ cmake path/to/aom -DCONFIG_TUNE_VMAF=1
353 The unit tests can be run at build time:
356 # Before running the make command the LIBAOM_TEST_DATA_PATH environment
358 # cmake build configuration directory.
359 $ cmake path/to/aom
361 # with multiple jobs will speed up the test run significantly.
367 The example tests require a bash shell and can be run in the following manner:
371 $ cmake path/to/aom
382 When making a change to the encoder run encoder tests to confirm that your
388 $ cmake path/to/aom -DCONFIG_INTERNAL_STATS=1
400 # This command line assumes that run_encodes.sh, its helper script
406 After making your change and creating the baseline clips, you'll need to run
414 # This command line assumes that run_encodes.sh, its helper script
442 # available, run cmake with the -G argument missing its
444 $ cmake path/to/aom -DENABLE_IDE_TEST_HOSTING=1 -G Xcode
456 $ cmake path/to/aom -G "Unix Makefiles"
461 The above make command will only download and verify the test data.
472 [`gsutil`](https://cloud.google.com/storage/docs/gsutil_install) command:
476 This command grants the `AllUsers` group READ access to the file named
480 add the name of the new test data file to `test/test_data_util.cmake` and add
482 checksum of a file can be calculated by running the `sha1sum` command on the
511 #### 2. Running the tests via the CMake build: {#running-the-tests-via-the-cmake-build}
519 # at test run time. This example will run the tests using 10 shards via
524 The maximum number of test targets that can run concurrently is determined by
526 CMake. A system with 24 cores can run 24 test shards using a value of 24 with
622 In addition to the local tests, many more (e.g. asan, tsan, valgrind) will run
647 The command line to upload your patch looks like this:
665 3. Use the same git push command as above to upload to Gerrit again for another
678 Sometimes this can’t be done automatically. If you run into this problem, you