README 4.54 KB
Newer Older
1
README - 30 May 2014
John Koleszar's avatar
John Koleszar committed
2

Paweł Hajdan's avatar
Paweł Hajdan committed
3
Welcome to the WebM VP8/VP9 Codec SDK!
John Koleszar's avatar
John Koleszar committed
4 5 6 7 8 9 10

COMPILING THE APPLICATIONS/LIBRARIES:
  The build system used is similar to autotools. Building generally consists of
  "configuring" with your desired build options, then using GNU make to build
  the application.

  1. Prerequisites
11

John Koleszar's avatar
John Koleszar committed
12 13
    * All x86 targets require the Yasm[1] assembler be installed.
    * All Windows builds require that Cygwin[2] be installed.
James Zern's avatar
James Zern committed
14 15 16
    * Building the documentation requires Doxygen[3]. If you do not
      have this package, the install-docs option will be disabled.
    * Downloading the data for the unit tests requires curl[4] and sha1sum.
17 18 19
      sha1sum is provided via the GNU coreutils, installed by default on
      many *nix platforms, as well as MinGW and Cygwin. If coreutils is not
      available, a compatible version of sha1sum can be built from
James Zern's avatar
James Zern committed
20
      source[5]. These requirements are optional if not running the unit
21
      tests.
22

John Koleszar's avatar
John Koleszar committed
23 24
    [1]: http://www.tortall.net/projects/yasm
    [2]: http://www.cygwin.com
James Zern's avatar
James Zern committed
25 26 27
    [3]: http://www.doxygen.org
    [4]: http://curl.haxx.se
    [5]: http://www.microbrew.org/tools/md5sha1sum/
28

John Koleszar's avatar
John Koleszar committed
29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
  2. Out-of-tree builds
  Out of tree builds are a supported method of building the application. For
  an out of tree build, the source tree is kept separate from the object
  files produced during compilation. For instance:

    $ mkdir build
    $ cd build
    $ ../libvpx/configure <options>
    $ make

  3. Configuration options
  The 'configure' script supports a number of options. The --help option can be
  used to get a list of supported options:
    $ ../libvpx/configure --help

  4. Cross development
  For cross development, the most notable option is the --target option. The
  most up-to-date list of supported targets can be found at the bottom of the
  --help output of the configure script. As of this writing, the list of
  available targets is:

50
    armv5te-android-gcc
John Koleszar's avatar
John Koleszar committed
51 52
    armv5te-linux-rvct
    armv5te-linux-gcc
Paweł Hajdan's avatar
Paweł Hajdan committed
53
    armv5te-none-rvct
John Koleszar's avatar
John Koleszar committed
54 55 56
    armv6-darwin-gcc
    armv6-linux-rvct
    armv6-linux-gcc
Paweł Hajdan's avatar
Paweł Hajdan committed
57
    armv6-none-rvct
58
    armv7-android-gcc
Paweł Hajdan's avatar
Paweł Hajdan committed
59
    armv7-darwin-gcc
John Koleszar's avatar
John Koleszar committed
60 61
    armv7-linux-rvct
    armv7-linux-gcc
Paweł Hajdan's avatar
Paweł Hajdan committed
62 63
    armv7-none-rvct
    armv7-win32-vs11
Yaowu Xu's avatar
Yaowu Xu committed
64
    armv7-win32-vs12
John Koleszar's avatar
John Koleszar committed
65 66 67
    mips32-linux-gcc
    ppc32-darwin8-gcc
    ppc32-darwin9-gcc
Paweł Hajdan's avatar
Paweł Hajdan committed
68
    ppc32-linux-gcc
John Koleszar's avatar
John Koleszar committed
69 70 71
    ppc64-darwin8-gcc
    ppc64-darwin9-gcc
    ppc64-linux-gcc
Paweł Hajdan's avatar
Paweł Hajdan committed
72 73
    sparc-solaris-gcc
    x86-android-gcc
John Koleszar's avatar
John Koleszar committed
74 75 76 77
    x86-darwin8-gcc
    x86-darwin8-icc
    x86-darwin9-gcc
    x86-darwin9-icc
Paweł Hajdan's avatar
Paweł Hajdan committed
78 79 80 81
    x86-darwin10-gcc
    x86-darwin11-gcc
    x86-darwin12-gcc
    x86-darwin13-gcc
John Koleszar's avatar
John Koleszar committed
82 83
    x86-linux-gcc
    x86-linux-icc
Paweł Hajdan's avatar
Paweł Hajdan committed
84
    x86-os2-gcc
John Koleszar's avatar
John Koleszar committed
85
    x86-solaris-gcc
Paweł Hajdan's avatar
Paweł Hajdan committed
86
    x86-win32-gcc
John Koleszar's avatar
John Koleszar committed
87 88
    x86-win32-vs7
    x86-win32-vs8
Paweł Hajdan's avatar
Paweł Hajdan committed
89 90 91
    x86-win32-vs9
    x86-win32-vs10
    x86-win32-vs11
Yaowu Xu's avatar
Yaowu Xu committed
92
    x86-win32-vs12
John Koleszar's avatar
John Koleszar committed
93
    x86_64-darwin9-gcc
Paweł Hajdan's avatar
Paweł Hajdan committed
94 95 96 97
    x86_64-darwin10-gcc
    x86_64-darwin11-gcc
    x86_64-darwin12-gcc
    x86_64-darwin13-gcc
John Koleszar's avatar
John Koleszar committed
98
    x86_64-linux-gcc
Paweł Hajdan's avatar
Paweł Hajdan committed
99
    x86_64-linux-icc
John Koleszar's avatar
John Koleszar committed
100
    x86_64-solaris-gcc
Paweł Hajdan's avatar
Paweł Hajdan committed
101
    x86_64-win64-gcc
John Koleszar's avatar
John Koleszar committed
102
    x86_64-win64-vs8
Paweł Hajdan's avatar
Paweł Hajdan committed
103 104 105
    x86_64-win64-vs9
    x86_64-win64-vs10
    x86_64-win64-vs11
Yaowu Xu's avatar
Yaowu Xu committed
106
    x86_64-win64-vs12
John Koleszar's avatar
John Koleszar committed
107 108
    universal-darwin8-gcc
    universal-darwin9-gcc
Paweł Hajdan's avatar
Paweł Hajdan committed
109 110 111 112
    universal-darwin10-gcc
    universal-darwin11-gcc
    universal-darwin12-gcc
    universal-darwin13-gcc
John Koleszar's avatar
John Koleszar committed
113 114 115 116 117 118 119 120 121
    generic-gnu

  The generic-gnu target, in conjunction with the CROSS environment variable,
  can be used to cross compile architectures that aren't explicitly listed, if
  the toolchain is a cross GNU (gcc/binutils) toolchain. Other POSIX toolchains
  will likely work as well. For instance, to build using the mipsel-linux-uclibc
  toolchain, the following command could be used (note, POSIX SH syntax, adapt
  to your shell as necessary):

Johann's avatar
Johann committed
122
    $ CROSS=mipsel-linux-uclibc- ../libvpx/configure
John Koleszar's avatar
John Koleszar committed
123 124 125 126 127 128 129

  In addition, the executables to be invoked can be overridden by specifying the
  environment variables: CC, AR, LD, AS, STRIP, NM. Additional flags can be
  passed to these executables with CFLAGS, LDFLAGS, and ASFLAGS.

  5. Configuration errors
  If the configuration step fails, the first step is to look in the error log.
130
  This defaults to config.log. This should give a good indication of what went
John Koleszar's avatar
John Koleszar committed
131 132
  wrong. If not, contact us for support.

133 134 135 136 137 138 139 140
VP8/VP9 TEST VECTORS:
  The test vectors can be downloaded and verified using the build system after
  running configure. To specify an alternate directory the
  LIBVPX_TEST_DATA_PATH environment variable can be used.

  $ ./configure --enable-unit-tests
  $ LIBVPX_TEST_DATA_PATH=../libvpx-test-data make testdata

John Koleszar's avatar
John Koleszar committed
141 142
SUPPORT
  This library is an open source project supported by its community. Please
143
  please email webm-discuss@webmproject.org for help.
John Koleszar's avatar
John Koleszar committed
144