Go to file
2012-08-14 09:21:40 -07:00
build Newline got lost in submission of "Partial import of "New RTCD implementation" from master branch." 2012-08-08 17:20:33 -07:00
examples Experimental code base simplification. 2012-02-15 16:08:47 +00:00
libmkv Restyle code 2012-07-17 11:46:03 -07:00
nestegg ivfdec: webm reader support 2010-10-25 22:01:40 -04:00
test A bit of temporary relief on encoder slowness 2012-08-07 14:06:11 -07:00
third_party x86inc: add some more format identifiers for elf file format recognition. 2012-06-20 09:49:15 -07:00
tools Import tools/ from master branch 2012-08-08 09:28:01 -07:00
vp8 Merge "Some build fixes" into experimental 2012-08-14 09:21:40 -07:00
vpx Dll build of libvpx 2012-07-23 14:51:21 -07:00
vpx_mem Restyle code 2012-07-17 11:46:03 -07:00
vpx_ports Restyle code 2012-07-17 11:46:03 -07:00
vpx_scale Merging and bug-fix in enhanced_interp experiment 2012-07-31 11:45:31 -07:00
.gitattributes Initial WebM release 2010-05-18 11:58:33 -04:00
.gitignore update gitignore 2010-09-28 10:09:01 -04:00
.mailmap Update .mailmap entry for Ralph Giles 2011-08-02 10:09:36 -04:00
all_builds.py Add script to test all builds. 2011-12-22 16:05:23 -08:00
args.c Restyle code 2012-07-17 11:46:03 -07:00
args.h Restyle code 2012-07-17 11:46:03 -07:00
AUTHORS Update AUTHORS 2011-08-02 10:09:59 -04:00
CHANGELOG Update CHANGELOG for v0.9.7-p1 2011-08-15 17:02:45 -04:00
configure Fix typo, which adds skip testing for 16x16 2012-08-13 16:28:11 -07:00
docs.mk Remove examples.doxy dep w/--disable-examples 2011-02-24 15:11:05 -08:00
example_xma.c Restyle code 2012-07-17 11:46:03 -07:00
examples.mk shared object on mac osx 2012-07-25 19:39:33 -07:00
keywords.dox Initial WebM release 2010-05-18 11:58:33 -04:00
libs.doxy_template Use WebM in copyright notice for consistency 2010-09-09 10:01:21 -04:00
libs.mk Partial import of "New RTCD implementation" from master branch. 2012-08-08 16:43:48 -07:00
LICENSE LICENSE: update with latest text 2010-06-04 16:19:40 -04:00
mainpage.dox documentation: minor cosmetics 2011-02-16 17:59:33 -08:00
md5_utils.c Restyle code 2012-07-17 11:46:03 -07:00
md5_utils.h Restyle code 2012-07-17 11:46:03 -07:00
PATENTS LICENSE: update with latest text 2010-06-04 16:19:40 -04:00
README purge wince configuration 2011-02-22 14:42:00 -05:00
solution.mk add unit test support via google test 2012-05-11 06:19:52 -07:00
tools_common.c Restyle code 2012-07-17 11:46:03 -07:00
tools_common.h Restyle code 2012-07-17 11:46:03 -07:00
usage_cx.dox Initial WebM release 2010-05-18 11:58:33 -04:00
usage_dx.dox Initial WebM release 2010-05-18 11:58:33 -04:00
usage.dox documentation: minor cosmetics 2011-02-16 17:59:33 -08:00
vp8_api1_migration.txt Initial WebM release 2010-05-18 11:58:33 -04:00
vpxdec.c Dll build of libvpx 2012-07-23 14:51:21 -07:00
vpxenc.c Added const specifier to remove warning 2012-07-24 12:50:03 -07:00
y4minput.c Restyle code 2012-07-17 11:46:03 -07:00
y4minput.h Restyle code 2012-07-17 11:46:03 -07:00

vpx Multi-Format Codec SDK
README - 19 May 2010

Welcome to the WebM VP8 Codec SDK!

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

    * All x86 targets require the Yasm[1] assembler be installed.
    * All Windows builds require that Cygwin[2] be installed.
    * Building the documentation requires PHP[3] and Doxygen[4]. If you do not
      have these packages, you must pass --disable-install-docs to the
      configure script.

    [1]: http://www.tortall.net/projects/yasm
    [2]: http://www.cygwin.com
    [3]: http://php.net
    [4]: http://www.doxygen.org

  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:

    armv5te-linux-rvct
    armv5te-linux-gcc
    armv5te-symbian-gcc
    armv6-darwin-gcc
    armv6-linux-rvct
    armv6-linux-gcc
    armv6-symbian-gcc
    iwmmxt-linux-rvct
    iwmmxt-linux-gcc
    iwmmxt2-linux-rvct
    iwmmxt2-linux-gcc
    armv7-linux-rvct
    armv7-linux-gcc
    mips32-linux-gcc
    ppc32-darwin8-gcc
    ppc32-darwin9-gcc
    ppc64-darwin8-gcc
    ppc64-darwin9-gcc
    ppc64-linux-gcc
    x86-darwin8-gcc
    x86-darwin8-icc
    x86-darwin9-gcc
    x86-darwin9-icc
    x86-linux-gcc
    x86-linux-icc
    x86-solaris-gcc
    x86-win32-vs7
    x86-win32-vs8
    x86_64-darwin9-gcc
    x86_64-linux-gcc
    x86_64-solaris-gcc
    x86_64-win64-vs8
    universal-darwin8-gcc
    universal-darwin9-gcc
    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):

    $ CROSS=mipsel-linux-uclibc- ../libvpx/configure

  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.
  This defaults to config.err. This should give a good indication of what went
  wrong. If not, contact us for support.

SUPPORT
  This library is an open source project supported by its community. Please
  please email webm-users@webmproject.org for help.