| OLD | NEW |
| 1 vpx Multi-Format Codec SDK | 1 vpx Multi-Format Codec SDK |
| 2 README - 1 August 2013 | 2 README - 1 August 2013 |
| 3 | 3 |
| 4 Welcome to the WebM VP8/VP9 Codec SDK! | 4 Welcome to the WebM VP8/VP9 Codec SDK! |
| 5 | 5 |
| 6 COMPILING THE APPLICATIONS/LIBRARIES: | 6 COMPILING THE APPLICATIONS/LIBRARIES: |
| 7 The build system used is similar to autotools. Building generally consists of | 7 The build system used is similar to autotools. Building generally consists of |
| 8 "configuring" with your desired build options, then using GNU make to build | 8 "configuring" with your desired build options, then using GNU make to build |
| 9 the application. | 9 the application. |
| 10 | 10 |
| 11 1. Prerequisites | 11 1. Prerequisites |
| 12 | 12 |
| 13 * All x86 targets require the Yasm[1] assembler be installed. | 13 * All x86 targets require the Yasm[1] assembler be installed. |
| 14 * All Windows builds require that Cygwin[2] be installed. | 14 * All Windows builds require that Cygwin[2] be installed. |
| 15 * Building the documentation requires PHP[3] and Doxygen[4]. If you do not | 15 * Building the documentation requires Doxygen[3]. If you do not |
| 16 have these packages, you must pass --disable-install-docs to the | 16 have this package, the install-docs option will be disabled. |
| 17 configure script. | 17 * Downloading the data for the unit tests requires curl[4] and sha1sum. |
| 18 * Downloading the data for the unit tests requires curl[5] and sha1sum. | |
| 19 sha1sum is provided via the GNU coreutils, installed by default on | 18 sha1sum is provided via the GNU coreutils, installed by default on |
| 20 many *nix platforms, as well as MinGW and Cygwin. If coreutils is not | 19 many *nix platforms, as well as MinGW and Cygwin. If coreutils is not |
| 21 available, a compatible version of sha1sum can be built from | 20 available, a compatible version of sha1sum can be built from |
| 22 source[6]. These requirements are optional if not running the unit | 21 source[5]. These requirements are optional if not running the unit |
| 23 tests. | 22 tests. |
| 24 | 23 |
| 25 [1]: http://www.tortall.net/projects/yasm | 24 [1]: http://www.tortall.net/projects/yasm |
| 26 [2]: http://www.cygwin.com | 25 [2]: http://www.cygwin.com |
| 27 [3]: http://php.net | 26 [3]: http://www.doxygen.org |
| 28 [4]: http://www.doxygen.org | 27 [4]: http://curl.haxx.se |
| 29 [5]: http://curl.haxx.se | 28 [5]: http://www.microbrew.org/tools/md5sha1sum/ |
| 30 [6]: http://www.microbrew.org/tools/md5sha1sum/ | |
| 31 | 29 |
| 32 2. Out-of-tree builds | 30 2. Out-of-tree builds |
| 33 Out of tree builds are a supported method of building the application. For | 31 Out of tree builds are a supported method of building the application. For |
| 34 an out of tree build, the source tree is kept separate from the object | 32 an out of tree build, the source tree is kept separate from the object |
| 35 files produced during compilation. For instance: | 33 files produced during compilation. For instance: |
| 36 | 34 |
| 37 $ mkdir build | 35 $ mkdir build |
| 38 $ cd build | 36 $ cd build |
| 39 $ ../libvpx/configure <options> | 37 $ ../libvpx/configure <options> |
| 40 $ make | 38 $ make |
| (...skipping 89 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 130 | 128 |
| 131 5. Configuration errors | 129 5. Configuration errors |
| 132 If the configuration step fails, the first step is to look in the error log. | 130 If the configuration step fails, the first step is to look in the error log. |
| 133 This defaults to config.log. This should give a good indication of what went | 131 This defaults to config.log. This should give a good indication of what went |
| 134 wrong. If not, contact us for support. | 132 wrong. If not, contact us for support. |
| 135 | 133 |
| 136 SUPPORT | 134 SUPPORT |
| 137 This library is an open source project supported by its community. Please | 135 This library is an open source project supported by its community. Please |
| 138 please email webm-discuss@webmproject.org for help. | 136 please email webm-discuss@webmproject.org for help. |
| 139 | 137 |
| OLD | NEW |