Lines Matching refs:turbo
1 Building libjpeg-turbo
17 build (2.11.08 does not work properly with libjpeg-turbo's x86-64 SIMD code
23 libjpeg-turbo, then YASM must be used when building libjpeg-turbo.
63 everything necessary to build libjpeg-turbo.
68 * If you intend to build libjpeg-turbo from the command line, then add the
98 necessarily be the same as the libjpeg-turbo source directory. You can create
100 libjpeg-turbo can be built from the same source tree using different compilers
102 directory, whereas *{source_directory}* refers to the libjpeg-turbo source
116 The following procedure will build libjpeg-turbo on Unix and Unix-like systems.
167 This will build either a 32-bit or a 64-bit version of libjpeg-turbo, depending
204 to build a 64-bit version of libjpeg-turbo. A separate build directory must be
209 build of libjpeg-turbo.
280 libjpeg-turbo that is API/ABI-compatible with libjpeg v7. Add `-DWITH_JPEG8=1`
281 to the CMake command line to build a version of libjpeg-turbo that is
289 the CMake command line to build a version of libjpeg-turbo that lacks the
298 included in this release of libjpeg-turbo. libjpeg-turbo's implementation is
315 build/test libjpeg-turbo, then (prior to running CMake) set the `JAVA_HOME`
393 Building libjpeg-turbo for iOS
398 advantage of libjpeg-turbo's SIMD extensions to significantly accelerate JPEG
399 compression/decompression. This section describes how to build libjpeg-turbo
406 (https://raw.githubusercontent.com/libjpeg-turbo/gas-preprocessor/master/gas-preprocessor.pl),
414 The following scripts demonstrate how to build libjpeg-turbo to run on the
467 The following scripts demonstrate how to build libjpeg-turbo to run on the
501 The following script demonstrates how to build libjpeg-turbo to run on the
525 Building libjpeg-turbo for Android
528 Building libjpeg-turbo for Android platforms requires v13b or later of the
642 will display all variables that are relevant to the libjpeg-turbo build, their
646 Installing libjpeg-turbo
649 You can use the build system to install libjpeg-turbo (as opposed to creating
653 the Visual Studio IDE) will uninstall libjpeg-turbo.
656 libjpeg-turbo into a directory of your choosing. If you don't specify
659 **c:\libjpeg-turbo**<br>
665 **c:\libjpeg-turbo-gcc**<br>
668 **c:\libjpeg-turbo-gcc64**<br>
671 **/opt/libjpeg-turbo**<br>
674 The default value of `CMAKE_INSTALL_PREFIX` causes the libjpeg-turbo files to
676 libjpeg-turbo binary packages. Changing the value of `CMAKE_INSTALL_PREFIX`
677 (for instance, to **/usr/local**) causes the libjpeg-turbo files to be
683 finer degree of control over where specific files in the libjpeg-turbo
746 libjpeg-turbo (default: *{source_directory}*/osxx86)
748 libjpeg-turbo (default: *{source_directory}*/iosarmv7)
750 libjpeg-turbo (default: *{source_directory}*/iosarmv7s)
752 libjpeg-turbo (default: *{source_directory}*/iosarmv8)
755 sub-builds of libjpeg-turbo (see "Build Recipes" and "Building libjpeg-turbo
758 libjpeg-turbo as an out-of-tree build, and build it. Once the primary build
788 The installer package (libjpeg-turbo-*{version}*[-gcc|-vc][64].exe) will be
802 The most common way to test libjpeg-turbo is by invoking `make test` (Un*x) or
806 libjpeg-turbo and libjpeg v6b. This also invokes the TurboJPEG unit tests,