blob: 0dfb0fe186b865c1d8699de3ed4e12ab5b70d464 [file] [log] [blame]
John Koleszar0ea50ce2010-05-18 11:58:33 -04001vpx Multi-Format Codec SDK
2README - 19 May 2010
3
4Welcome to the WebM VP8 Codec SDK!
5
6COMPILING THE APPLICATIONS/LIBRARIES:
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
9 the application.
10
11 1. Prerequisites
John Koleszar94c52e42010-06-18 12:39:21 -040012
John Koleszar0ea50ce2010-05-18 11:58:33 -040013 * All x86 targets require the Yasm[1] assembler 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
16 have these packages, you must pass --disable-install-docs to the
17 configure script.
John Koleszar94c52e42010-06-18 12:39:21 -040018
John Koleszar0ea50ce2010-05-18 11:58:33 -040019 [1]: http://www.tortall.net/projects/yasm
20 [2]: http://www.cygwin.com
21 [3]: http://php.net
22 [4]: http://www.doxygen.org
John Koleszar94c52e42010-06-18 12:39:21 -040023
John Koleszar0ea50ce2010-05-18 11:58:33 -040024 2. Out-of-tree builds
25 Out of tree builds are a supported method of building the application. For
26 an out of tree build, the source tree is kept separate from the object
27 files produced during compilation. For instance:
28
29 $ mkdir build
30 $ cd build
31 $ ../libvpx/configure <options>
32 $ make
33
34 3. Configuration options
35 The 'configure' script supports a number of options. The --help option can be
36 used to get a list of supported options:
37 $ ../libvpx/configure --help
38
39 4. Cross development
40 For cross development, the most notable option is the --target option. The
41 most up-to-date list of supported targets can be found at the bottom of the
42 --help output of the configure script. As of this writing, the list of
43 available targets is:
44
Fritz Koenigd8305732012-01-06 11:50:05 -080045 armv5te-android-gcc
John Koleszar0ea50ce2010-05-18 11:58:33 -040046 armv5te-linux-rvct
47 armv5te-linux-gcc
John Koleszar0ea50ce2010-05-18 11:58:33 -040048 armv6-darwin-gcc
49 armv6-linux-rvct
50 armv6-linux-gcc
Fritz Koenigd8305732012-01-06 11:50:05 -080051 armv7-android-gcc
John Koleszar0ea50ce2010-05-18 11:58:33 -040052 armv7-linux-rvct
53 armv7-linux-gcc
54 mips32-linux-gcc
55 ppc32-darwin8-gcc
56 ppc32-darwin9-gcc
57 ppc64-darwin8-gcc
58 ppc64-darwin9-gcc
59 ppc64-linux-gcc
60 x86-darwin8-gcc
61 x86-darwin8-icc
62 x86-darwin9-gcc
63 x86-darwin9-icc
64 x86-linux-gcc
65 x86-linux-icc
66 x86-solaris-gcc
67 x86-win32-vs7
68 x86-win32-vs8
69 x86_64-darwin9-gcc
70 x86_64-linux-gcc
71 x86_64-solaris-gcc
72 x86_64-win64-vs8
73 universal-darwin8-gcc
74 universal-darwin9-gcc
75 generic-gnu
76
77 The generic-gnu target, in conjunction with the CROSS environment variable,
78 can be used to cross compile architectures that aren't explicitly listed, if
79 the toolchain is a cross GNU (gcc/binutils) toolchain. Other POSIX toolchains
80 will likely work as well. For instance, to build using the mipsel-linux-uclibc
81 toolchain, the following command could be used (note, POSIX SH syntax, adapt
82 to your shell as necessary):
83
Johanna31a58d2010-10-07 14:13:36 -040084 $ CROSS=mipsel-linux-uclibc- ../libvpx/configure
John Koleszar0ea50ce2010-05-18 11:58:33 -040085
86 In addition, the executables to be invoked can be overridden by specifying the
87 environment variables: CC, AR, LD, AS, STRIP, NM. Additional flags can be
88 passed to these executables with CFLAGS, LDFLAGS, and ASFLAGS.
89
90 5. Configuration errors
91 If the configuration step fails, the first step is to look in the error log.
92 This defaults to config.err. This should give a good indication of what went
93 wrong. If not, contact us for support.
94
95SUPPORT
96 This library is an open source project supported by its community. Please
97 please email webm-users@webmproject.org for help.
98