1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/media/libmkv/README Wed Dec 31 06:09:35 2014 +0100
1.3 @@ -0,0 +1,139 @@
1.4 +vpx Multi-Format Codec SDK
1.5 +README - 1 August 2013
1.6 +
1.7 +Welcome to the WebM VP8/VP9 Codec SDK!
1.8 +
1.9 +COMPILING THE APPLICATIONS/LIBRARIES:
1.10 + The build system used is similar to autotools. Building generally consists of
1.11 + "configuring" with your desired build options, then using GNU make to build
1.12 + the application.
1.13 +
1.14 + 1. Prerequisites
1.15 +
1.16 + * All x86 targets require the Yasm[1] assembler be installed.
1.17 + * All Windows builds require that Cygwin[2] be installed.
1.18 + * Building the documentation requires PHP[3] and Doxygen[4]. If you do not
1.19 + have these packages, you must pass --disable-install-docs to the
1.20 + configure script.
1.21 + * Downloading the data for the unit tests requires curl[5] and sha1sum.
1.22 + sha1sum is provided via the GNU coreutils, installed by default on
1.23 + many *nix platforms, as well as MinGW and Cygwin. If coreutils is not
1.24 + available, a compatible version of sha1sum can be built from
1.25 + source[6]. These requirements are optional if not running the unit
1.26 + tests.
1.27 +
1.28 + [1]: http://www.tortall.net/projects/yasm
1.29 + [2]: http://www.cygwin.com
1.30 + [3]: http://php.net
1.31 + [4]: http://www.doxygen.org
1.32 + [5]: http://curl.haxx.se
1.33 + [6]: http://www.microbrew.org/tools/md5sha1sum/
1.34 +
1.35 + 2. Out-of-tree builds
1.36 + Out of tree builds are a supported method of building the application. For
1.37 + an out of tree build, the source tree is kept separate from the object
1.38 + files produced during compilation. For instance:
1.39 +
1.40 + $ mkdir build
1.41 + $ cd build
1.42 + $ ../libvpx/configure <options>
1.43 + $ make
1.44 +
1.45 + 3. Configuration options
1.46 + The 'configure' script supports a number of options. The --help option can be
1.47 + used to get a list of supported options:
1.48 + $ ../libvpx/configure --help
1.49 +
1.50 + 4. Cross development
1.51 + For cross development, the most notable option is the --target option. The
1.52 + most up-to-date list of supported targets can be found at the bottom of the
1.53 + --help output of the configure script. As of this writing, the list of
1.54 + available targets is:
1.55 +
1.56 + armv5te-android-gcc
1.57 + armv5te-linux-rvct
1.58 + armv5te-linux-gcc
1.59 + armv5te-none-rvct
1.60 + armv6-darwin-gcc
1.61 + armv6-linux-rvct
1.62 + armv6-linux-gcc
1.63 + armv6-none-rvct
1.64 + armv7-android-gcc
1.65 + armv7-darwin-gcc
1.66 + armv7-linux-rvct
1.67 + armv7-linux-gcc
1.68 + armv7-none-rvct
1.69 + armv7-win32-vs11
1.70 + armv7-win32-vs12
1.71 + mips32-linux-gcc
1.72 + ppc32-darwin8-gcc
1.73 + ppc32-darwin9-gcc
1.74 + ppc32-linux-gcc
1.75 + ppc64-darwin8-gcc
1.76 + ppc64-darwin9-gcc
1.77 + ppc64-linux-gcc
1.78 + sparc-solaris-gcc
1.79 + x86-android-gcc
1.80 + x86-darwin8-gcc
1.81 + x86-darwin8-icc
1.82 + x86-darwin9-gcc
1.83 + x86-darwin9-icc
1.84 + x86-darwin10-gcc
1.85 + x86-darwin11-gcc
1.86 + x86-darwin12-gcc
1.87 + x86-darwin13-gcc
1.88 + x86-linux-gcc
1.89 + x86-linux-icc
1.90 + x86-os2-gcc
1.91 + x86-solaris-gcc
1.92 + x86-win32-gcc
1.93 + x86-win32-vs7
1.94 + x86-win32-vs8
1.95 + x86-win32-vs9
1.96 + x86-win32-vs10
1.97 + x86-win32-vs11
1.98 + x86-win32-vs12
1.99 + x86_64-darwin9-gcc
1.100 + x86_64-darwin10-gcc
1.101 + x86_64-darwin11-gcc
1.102 + x86_64-darwin12-gcc
1.103 + x86_64-darwin13-gcc
1.104 + x86_64-linux-gcc
1.105 + x86_64-linux-icc
1.106 + x86_64-solaris-gcc
1.107 + x86_64-win64-gcc
1.108 + x86_64-win64-vs8
1.109 + x86_64-win64-vs9
1.110 + x86_64-win64-vs10
1.111 + x86_64-win64-vs11
1.112 + x86_64-win64-vs12
1.113 + universal-darwin8-gcc
1.114 + universal-darwin9-gcc
1.115 + universal-darwin10-gcc
1.116 + universal-darwin11-gcc
1.117 + universal-darwin12-gcc
1.118 + universal-darwin13-gcc
1.119 + generic-gnu
1.120 +
1.121 + The generic-gnu target, in conjunction with the CROSS environment variable,
1.122 + can be used to cross compile architectures that aren't explicitly listed, if
1.123 + the toolchain is a cross GNU (gcc/binutils) toolchain. Other POSIX toolchains
1.124 + will likely work as well. For instance, to build using the mipsel-linux-uclibc
1.125 + toolchain, the following command could be used (note, POSIX SH syntax, adapt
1.126 + to your shell as necessary):
1.127 +
1.128 + $ CROSS=mipsel-linux-uclibc- ../libvpx/configure
1.129 +
1.130 + In addition, the executables to be invoked can be overridden by specifying the
1.131 + environment variables: CC, AR, LD, AS, STRIP, NM. Additional flags can be
1.132 + passed to these executables with CFLAGS, LDFLAGS, and ASFLAGS.
1.133 +
1.134 + 5. Configuration errors
1.135 + If the configuration step fails, the first step is to look in the error log.
1.136 + This defaults to config.log. This should give a good indication of what went
1.137 + wrong. If not, contact us for support.
1.138 +
1.139 +SUPPORT
1.140 + This library is an open source project supported by its community. Please
1.141 + please email webm-discuss@webmproject.org for help.
1.142 +
