Lines Matching full:cmake
255 Use CMake (see recipes below)
547 - [CMake](http://www.cmake.org) v2.8.11 or later
591 which CMake is executed (the "binary directory"), and this directory need not
603 NOTE: The build procedures below assume that CMake is invoked from the command
604 line, but all of these procedures can be adapted to the CMake GUI as
611 cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release [additional CMake flags] {source_directory}
643 Choose the appropriate CMake generator option for your version of Visual Studio
644 (run `cmake` with no arguments for a list of available generators.) For
648 cmake -G"Visual Studio 10" [additional CMake flags] {source_directory}
690 cmake -G"MSYS Makefiles" [additional CMake flags] {source_directory}
719 Add `-DCMAKE_BUILD_TYPE=Debug` to the CMake command line. Or, if building
726 Add `-DWITH_JPEG7=1` to the CMake command line to build a version of
728 to the CMake command line to build a version of libjpeg-turbo that is
736 the CMake command line to build a version of libjpeg-turbo that lacks the
749 add `-DWITH_ARITH_ENC=0` or `-DWITH_ARITH_DEC=0` to the CMake command line to
755 Add `-DWITH_JAVA=1` to the CMake command line to incorporate an optional Java
762 build/test libjpeg-turbo, then (prior to running CMake) set the `JAVA_HOME`
765 CMake variables can also be used to specify alternate commands or locations for
766 javac, jar, and java (respectively.) You can also set the `JAVACFLAGS` CMake
777 Create a file called **toolchain.cmake** under *{build_directory}*, with the
789 cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=toolchain.cmake \
790 [additional CMake flags] {source_directory}
796 Create a file called **toolchain.cmake** under *{build_directory}*, with the
808 cmake -G"Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=toolchain.cmake \
809 [additional CMake flags] {source_directory}
822 The `CMAKE_INSTALL_PREFIX` CMake variable can be modified in order to install
