Lines Matching full:cmake
11 - [CMake](http://www.cmake.org) v2.8.12 or later
58 * If using JDK 11 or later, CMake 3.10.x or later must also be used.
95 * If using JDK 11 or later, CMake 3.10.x or later must also be used.
102 which CMake is executed (the "binary directory"), and this directory need not
114 NOTE: The build procedures below assume that CMake is invoked from the command
115 line, but all of these procedures can be adapted to the CMake GUI as
126 cmake -G"Unix Makefiles" [additional CMake flags] {source_directory}
169 cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release [additional CMake flags] {source_directory}
201 Choose the appropriate CMake generator option for your version of Visual Studio
202 (run `cmake` with no arguments for a list of available generators.) For
206 cmake -G"Visual Studio 10" [additional CMake flags] {source_directory}
248 cmake -G"MSYS Makefiles" [additional CMake flags] {source_directory}
277 Add `-DCMAKE_BUILD_TYPE=Debug` to the CMake command line. Or, if building
284 Add `-DWITH_JPEG7=1` to the CMake command line to build a version of
286 to the CMake command line to build a version of libjpeg-turbo that is
294 the CMake command line to build a version of libjpeg-turbo that lacks the
307 add `-DWITH_ARITH_ENC=0` or `-DWITH_ARITH_DEC=0` to the CMake command line to
313 Add `-DWITH_JAVA=1` to the CMake command line to incorporate an optional Java
320 build/test libjpeg-turbo, then (prior to running CMake) set the `JAVA_HOME`
323 CMake variables can also be used to specify alternate commands or locations for
325 `CMAKE_JAVA_COMPILE_FLAGS` CMake variable or the `JAVAFLAGS` environment
327 building the TurboJPEG classes, and the `JAVAARGS` CMake variable to specify
339 CMake:
348 CMake:
356 On Un*x systems, prior to running CMake, you can set the `CC` environment
362 Create a file called **toolchain.cmake** under *{build_directory}*, with the
374 cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=toolchain.cmake \
375 [additional CMake flags] {source_directory}
381 Create a file called **toolchain.cmake** under *{build_directory}*, with the
393 cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=toolchain.cmake \
394 [additional CMake flags] {source_directory}
430 cat <<EOF >toolchain.cmake
436 cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=toolchain.cmake \
438 [additional CMake flags] {source_directory}
456 cat <<EOF >toolchain.cmake
462 cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=toolchain.cmake \
464 [additional CMake flags] {source_directory}
483 cat <<EOF >toolchain.cmake
489 cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=toolchain.cmake \
491 [additional CMake flags] {source_directory}
515 cat <<EOF >toolchain.cmake
521 cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=toolchain.cmake \
523 [additional CMake flags] {source_directory}
551 cmake -G"Unix Makefiles" \
557 -DCMAKE_TOOLCHAIN_FILE=${NDK_PATH}/build/cmake/android.toolchain.cmake \
558 [additional CMake flags] {source_directory}
576 cmake -G"Unix Makefiles" \
582 -DCMAKE_TOOLCHAIN_FILE=${NDK_PATH}/build/cmake/android.toolchain.cmake \
583 [additional CMake flags] {source_directory}
601 cmake -G"Unix Makefiles" \
605 -DCMAKE_TOOLCHAIN_FILE=${NDK_PATH}/build/cmake/android.toolchain.cmake \
606 [additional CMake flags] {source_directory}
624 cmake -G"Unix Makefiles" \
628 -DCMAKE_TOOLCHAIN_FILE=${NDK_PATH}/build/cmake/android.toolchain.cmake \
629 [additional CMake flags] {source_directory}
633 Advanced CMake Options
636 To list and configure other CMake options not specifically mentioned in this
643 cmake-gui {source_directory}
646 text-based interactive version of CMake, and CMake-GUI is a GUI version. Both
660 The `CMAKE_INSTALL_PREFIX` CMake variable can be modified in order to install
687 `CMAKE_INSTALL_LIBDIR`, and `CMAKE_INSTALL_MANDIR` CMake variables allow a
692 documentation to be installed in **${CMAKE\_INSTALL\_PREFIX}/doc**.) If a
696 **\<CMAKE\_INSTALL\_DATAROOTDIR\>/man**.
699 CMake command line, you must specify that the variable is of type `PATH`.
702 cmake -G"{generator type}" -DCMAKE_INSTALL_LIBDIR:PATH=lib {source_directory}
704 Otherwise, CMake will assume that the path is relative to the build directory
746 binaries. The following CMake variables control which architectures are
759 You should first use CMake to configure i386, ARMv7, ARMv7s, and/or ARMv8
762 aforementioned CMake variables. Next, configure the primary build of