Lines Matching full:cmake
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
82 CMake replaces the configure step typical of many projects. Running CMake will
83 produce configuration and build files for the currently selected CMake
88 $ cmake path/to/aom
95 applies: On systems where cc and c++ are present in $PATH at the time CMake is
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`.
122 CMake built in variable `BUILD_SHARED_LIBS`:
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
164 architecture will be considered cross compiles. The AV1 CMake build handles
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
213 Sanitizer integration is built-in to the CMake build system. To enable a
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
302 # executed cmake.
319 $ cmake path/to/aom \
332 $ cmake path/to/aom -DCONFIG_TUNE_VMAF=1
358 # cmake build configuration directory.
359 $ cmake path/to/aom
360 # Note: The AV1 CMake build creates many test targets. Running make
371 $ cmake path/to/aom
388 $ cmake path/to/aom -DCONFIG_INTERNAL_STATS=1
433 By default the generated projects files created by CMake will not include the
438 `ENABLE_IDE_TEST_HOSTING` variable must be enabled at CMake generation time:
442 # available, run cmake with the -G argument missing its
444 $ cmake path/to/aom -DENABLE_IDE_TEST_HOSTING=1 -G Xcode
449 The fastest and easiest way to obtain the test data is to use CMake to generate
456 $ cmake path/to/aom -G "Unix Makefiles"
480 add the name of the new test data file to `test/test_data_util.cmake` and add
511 #### 2. Running the tests via the CMake build: {#running-the-tests-via-the-cmake-build}
526 CMake. A system with 24 cores can run 24 test shards using a value of 24 with
527 the `-j` parameter. When CMake is unable to detect the number of cores 10 shards