NameDateSize

..12-Mar-20154 KiB

.mailmap12-Mar-2015905

args.c12-Mar-20156.1 KiB

args.h12-Mar-20151.6 KiB

AUTHORS12-Mar-20153.5 KiB

build/12-Mar-20154 KiB

CHANGELOG12-Mar-201524 KiB

configure12-Mar-201523.4 KiB

docs.mk12-Mar-20151.7 KiB

examples/12-Mar-20154 KiB

examples.mk12-Mar-201515.7 KiB

ivfdec.c12-Mar-20153.1 KiB

ivfdec.h12-Mar-2015747

ivfenc.c12-Mar-20151.8 KiB

ivfenc.h12-Mar-2015970

keywords.dox12-Mar-20152.1 KiB

libs.doxy_template12-Mar-201553 KiB

libs.mk12-Mar-201518.8 KiB

LICENSE12-Mar-20151.5 KiB

mainpage.dox12-Mar-20151.5 KiB

md5_utils.c12-Mar-20157.4 KiB

md5_utils.h12-Mar-20151.4 KiB

PATENTS12-Mar-20151.3 KiB

rate_hist.c12-Mar-20157.4 KiB

rate_hist.h12-Mar-20151.1 KiB

README12-Mar-20154.3 KiB

solution.mk12-Mar-20151.2 KiB

test/12-Mar-20154 KiB

third_party/12-Mar-20154 KiB

tools/12-Mar-20154 KiB

tools_common.c12-Mar-20156.3 KiB

tools_common.h12-Mar-20153.7 KiB

usage.dox12-Mar-201511 KiB

usage_cx.dox12-Mar-2015447

usage_dx.dox12-Mar-20153.6 KiB

video_common.h12-Mar-2015647

video_reader.c12-Mar-20152.2 KiB

video_reader.h12-Mar-20151.9 KiB

video_writer.c12-Mar-20152.1 KiB

video_writer.h12-Mar-20151.4 KiB

vp8/12-Mar-20154 KiB

vp9/12-Mar-20154 KiB

vpx/12-Mar-20154 KiB

vpx_mem/12-Mar-20154 KiB

vpx_ports/12-Mar-20154 KiB

vpx_scale/12-Mar-20154 KiB

vpxdec.c12-Mar-201531.7 KiB

vpxenc.c12-Mar-201563.6 KiB

vpxenc.h12-Mar-20151.2 KiB

vpxstats.c12-Mar-20153 KiB

vpxstats.h12-Mar-20151.1 KiB

warnings.c12-Mar-20153.4 KiB

warnings.h12-Mar-2015992

webmdec.c12-Mar-20154.9 KiB

webmdec.h12-Mar-20151.2 KiB

webmenc.c12-Mar-201510.2 KiB

webmenc.h12-Mar-20152.3 KiB

y4menc.c12-Mar-20151.1 KiB

y4menc.h12-Mar-2015875

y4minput.c12-Mar-201535.5 KiB

y4minput.h12-Mar-20152 KiB

README

1vpx Multi-Format Codec SDK
2README - 1 August 2013
3
4Welcome to the WebM VP8/VP9 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
12
13    * 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.
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
20      many *nix platforms, as well as MinGW and Cygwin. If coreutils is not
21      available, a compatible version of sha1sum can be built from
22      source[6]. These requirements are optional if not running the unit
23      tests.
24
25    [1]: http://www.tortall.net/projects/yasm
26    [2]: http://www.cygwin.com
27    [3]: http://php.net
28    [4]: http://www.doxygen.org
29    [5]: http://curl.haxx.se
30    [6]: http://www.microbrew.org/tools/md5sha1sum/
31
32  2. Out-of-tree builds
33  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
35  files produced during compilation. For instance:
36
37    $ mkdir build
38    $ cd build
39    $ ../libvpx/configure <options>
40    $ make
41
42  3. Configuration options
43  The 'configure' script supports a number of options. The --help option can be
44  used to get a list of supported options:
45    $ ../libvpx/configure --help
46
47  4. Cross development
48  For cross development, the most notable option is the --target option. The
49  most up-to-date list of supported targets can be found at the bottom of the
50  --help output of the configure script. As of this writing, the list of
51  available targets is:
52
53    armv5te-android-gcc
54    armv5te-linux-rvct
55    armv5te-linux-gcc
56    armv5te-none-rvct
57    armv6-darwin-gcc
58    armv6-linux-rvct
59    armv6-linux-gcc
60    armv6-none-rvct
61    armv7-android-gcc
62    armv7-darwin-gcc
63    armv7-linux-rvct
64    armv7-linux-gcc
65    armv7-none-rvct
66    armv7-win32-vs11
67    armv7-win32-vs12
68    mips32-linux-gcc
69    ppc32-darwin8-gcc
70    ppc32-darwin9-gcc
71    ppc32-linux-gcc
72    ppc64-darwin8-gcc
73    ppc64-darwin9-gcc
74    ppc64-linux-gcc
75    sparc-solaris-gcc
76    x86-android-gcc
77    x86-darwin8-gcc
78    x86-darwin8-icc
79    x86-darwin9-gcc
80    x86-darwin9-icc
81    x86-darwin10-gcc
82    x86-darwin11-gcc
83    x86-darwin12-gcc
84    x86-darwin13-gcc
85    x86-linux-gcc
86    x86-linux-icc
87    x86-os2-gcc
88    x86-solaris-gcc
89    x86-win32-gcc
90    x86-win32-vs7
91    x86-win32-vs8
92    x86-win32-vs9
93    x86-win32-vs10
94    x86-win32-vs11
95    x86-win32-vs12
96    x86_64-darwin9-gcc
97    x86_64-darwin10-gcc
98    x86_64-darwin11-gcc
99    x86_64-darwin12-gcc
100    x86_64-darwin13-gcc
101    x86_64-linux-gcc
102    x86_64-linux-icc
103    x86_64-solaris-gcc
104    x86_64-win64-gcc
105    x86_64-win64-vs8
106    x86_64-win64-vs9
107    x86_64-win64-vs10
108    x86_64-win64-vs11
109    x86_64-win64-vs12
110    universal-darwin8-gcc
111    universal-darwin9-gcc
112    universal-darwin10-gcc
113    universal-darwin11-gcc
114    universal-darwin12-gcc
115    universal-darwin13-gcc
116    generic-gnu
117
118  The generic-gnu target, in conjunction with the CROSS environment variable,
119  can be used to cross compile architectures that aren't explicitly listed, if
120  the toolchain is a cross GNU (gcc/binutils) toolchain. Other POSIX toolchains
121  will likely work as well. For instance, to build using the mipsel-linux-uclibc
122  toolchain, the following command could be used (note, POSIX SH syntax, adapt
123  to your shell as necessary):
124
125    $ CROSS=mipsel-linux-uclibc- ../libvpx/configure
126
127  In addition, the executables to be invoked can be overridden by specifying the
128  environment variables: CC, AR, LD, AS, STRIP, NM. Additional flags can be
129  passed to these executables with CFLAGS, LDFLAGS, and ASFLAGS.
130
131  5. Configuration errors
132  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
134  wrong. If not, contact us for support.
135
136SUPPORT
137  This library is an open source project supported by its community. Please
138  please email webm-discuss@webmproject.org for help.
139
140