Alliance for Open Media Video Codec reference implementation (Mozilla branch)
Перейти к файлу
Dmitry Kovalev 2b089f149a Merge "Removing unused static arrays from vp9_reatectrl.c." 2013-07-20 22:39:33 -07:00
build Make libvpx compile on OSX 10.9 (Mavericks) 2013-07-19 21:22:18 +02:00
examples
libmkv
nestegg halloc: Cast the offsetof macro to ptrdiff_t before negating 2013-06-07 10:18:59 +03:00
test cosmetics: tile_independence_test: fix formatting 2013-07-18 16:00:01 -07:00
third_party Fix mingw build error 2013-06-04 13:08:54 -07:00
tools
vp8 use consistent framerate naming 2013-07-16 14:12:47 -07:00
vp9 Merge "Removing unused static arrays from vp9_reatectrl.c." 2013-07-20 22:39:33 -07:00
vpx vp[89]_dx_iface: factorize vp8_mmap_*() 2013-07-11 23:01:26 -07:00
vpx_mem
vpx_ports vpx_ports/x86.h: de-dup #elif block 2013-06-17 21:58:00 -07:00
vpx_scale added missed replacement 2013-07-16 17:12:45 -07:00
.gitattributes
.gitignore .gitignore: add gcov files 2013-06-24 15:59:32 -07:00
.mailmap
AUTHORS
CHANGELOG
LICENSE
PATENTS
README
args.c
args.h
configure Make libvpx compile on OSX 10.9 (Mavericks) 2013-07-19 21:22:18 +02:00
docs.mk
example_xma.c
examples.mk msvs: Don't link to winmm.lib 2013-05-21 09:57:04 +03:00
keywords.dox
libs.doxy_template
libs.mk test_libvpx: disable pthreads in gtest for win targets 2013-06-26 18:35:11 -07:00
mainpage.dox
md5_utils.c
md5_utils.h
solution.mk msvs: Support producing both vcproj and vcxproj depending on configure variables 2013-05-21 09:57:02 +03:00
tools_common.c
tools_common.h
usage.dox
usage_cx.dox
usage_dx.dox
vp8_multi_resolution_encoder.c
vp8_scalable_patterns.c
vpxdec.c vpxdec: add --loops option 2013-06-12 16:09:20 -07:00
vpxenc.c vpxenc: send usage to stderr 2013-06-25 09:17:41 -07:00
y4minput.c
y4minput.h

README

vpx Multi-Format Codec SDK
README - 21 June 2012

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.
    * Downloading the data for the unit tests requires curl[5] and sha1sum.
      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
      source[6]. These requirements are optional if not running the unit
      tests.

    [1]: http://www.tortall.net/projects/yasm
    [2]: http://www.cygwin.com
    [3]: http://php.net
    [4]: http://www.doxygen.org
    [5]: http://curl.haxx.se
    [6]: http://www.microbrew.org/tools/md5sha1sum/

  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-android-gcc
    armv5te-linux-rvct
    armv5te-linux-gcc
    armv6-darwin-gcc
    armv6-linux-rvct
    armv6-linux-gcc
    armv7-android-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-discuss@webmproject.org for help.