@@ -13,13 +13,13 @@ Build Requirements
1313 [ MacPorts] ( http://www.MacPorts.org ) .
1414
1515- NASM or YASM (if building x86 or x86-64 SIMD extensions)
16- * NASM 0.98, or 2.01 or later is required for an x86 build (0.99 and 2.00 do
17- not work properly with libjpeg-turbo's x86 SIMD code.)
18- * NASM 2.00 or later is required for an x86-64 build.
19- * NASM 2.07, or 2.11.09 or later is required for an x86-64 Mac build
20- (2.11.08 does not work properly with libjpeg-turbo's x86-64 SIMD code when
21- building macho64 objects.) NASM or YASM can be obtained from
22- [ MacPorts] ( http://www.MacPorts .org ) .
16+ * If using NASM, 0.98, or 2.01 or later is required for an x86 build (0.99
17+ and 2.00 do not work properly with libjpeg-turbo's x86 SIMD code.)
18+ * If using NASM, 2.00 or later is required for an x86-64 build.
19+ * If using NASM, 2.07 or later (except 2.11.08) is required for an x86-64
20+ Mac build (2.11.08 does not work properly with libjpeg-turbo's x86-64 SIMD
21+ code when building macho64 objects.) NASM or YASM can be obtained from
22+ [ MacPorts] ( http://www.macports .org/ ) .
2323
2424 The binary RPMs released by the NASM project do not work on older Linux
2525 systems, such as Red Hat Enterprise Linux 4. On such systems, you can
@@ -458,11 +458,12 @@ Building on Windows (Visual C++ or MinGW)
458458Build Requirements
459459------------------
460460
461- - [ CMake] ( http://www.cmake.org ) v2.8.8 or later
461+ - [ CMake] ( http://www.cmake.org ) v2.8.11 or later
462462
463- - [ NASM] ( http://www.nasm.us/ ) 0.98 or later (NASM 2.05 or later is required for
464- a 64-bit build)
465- * nasm.exe should be in your ` PATH ` .
463+ - [ NASM] ( http://www.nasm.us ) or [ YASM] ( http://yasm.tortall.net )
464+ * If using NASM, 0.98 or later is required for an x86 build.
465+ * If using NASM, 2.05 or later is required for an x86-64 build.
466+ * nasm.exe/yasm.exe should be in your ` PATH ` .
466467
467468- Microsoft Visual C++ 2005 or later
468469
@@ -668,11 +669,11 @@ front-end classes to support it. This allows the TurboJPEG shared library to
668669be used directly from Java applications. See [ java/README] ( java/README ) for
669670more details.
670671
671- If you are using CMake 2.8, you can set the ` Java_JAVAC_EXECUTABLE ` ,
672- ` Java_JAVA_EXECUTABLE ` , and ` Java_JAR_EXECUTABLE ` CMake variables to specify
673- alternate commands or locations for javac, jar, and java (respectively.) You
674- can also set the ` JAVACFLAGS ` CMake variable to specify arguments that should
675- be passed to the Java compiler when building the front-end classes.
672+ You can set the ` Java_JAVAC_EXECUTABLE ` , ` Java_JAVA_EXECUTABLE ` , and
673+ ` Java_JAR_EXECUTABLE ` CMake variables to specify alternate commands or
674+ locations for javac, jar, and java (respectively.) You can also set the
675+ ` JAVACFLAGS ` CMake variable to specify arguments that should be passed to the
676+ Java compiler when building the front-end classes.
676677
677678
678679Installing libjpeg-turbo
0 commit comments