2011-12-03 21:25:04 +01:00
|
|
|
\input texinfo @c -*- texinfo -*-
|
|
|
|
|
|
|
|
@settitle Platform Specific information
|
|
|
|
@titlepage
|
|
|
|
@center @titlefont{Platform Specific information}
|
|
|
|
@end titlepage
|
|
|
|
|
|
|
|
@top
|
|
|
|
|
|
|
|
@contents
|
|
|
|
|
|
|
|
@chapter Unix-like
|
|
|
|
|
|
|
|
Some parts of Libav cannot be built with version 2.15 of the GNU
|
|
|
|
assembler which is still provided by a few AMD64 distributions. To
|
|
|
|
make sure your compiler really uses the required version of gas
|
|
|
|
after a binutils upgrade, run:
|
|
|
|
|
|
|
|
@example
|
|
|
|
$(gcc -print-prog-name=as) --version
|
|
|
|
@end example
|
|
|
|
|
|
|
|
If not, then you should install a different compiler that has no
|
|
|
|
hard-coded path to gas. In the worst case pass @code{--disable-asm}
|
|
|
|
to configure.
|
|
|
|
|
|
|
|
@section BSD
|
|
|
|
|
|
|
|
BSD make will not build Libav, you need to install and use GNU Make
|
2012-05-16 19:24:39 +02:00
|
|
|
(@command{gmake}).
|
2011-12-03 21:25:04 +01:00
|
|
|
|
|
|
|
@section (Open)Solaris
|
|
|
|
|
2012-05-16 19:24:39 +02:00
|
|
|
GNU Make is required to build Libav, so you have to invoke (@command{gmake}),
|
2011-12-03 21:25:04 +01:00
|
|
|
standard Solaris Make will not work. When building with a non-c99 front-end
|
|
|
|
(gcc, generic suncc) add either @code{--extra-libs=/usr/lib/values-xpg6.o}
|
|
|
|
or @code{--extra-libs=/usr/lib/64/values-xpg6.o} to the configure options
|
|
|
|
since the libc is not c99-compliant by default. The probes performed by
|
|
|
|
configure may raise an exception leading to the death of configure itself
|
|
|
|
due to a bug in the system shell. Simply invoke a different shell such as
|
|
|
|
bash directly to work around this:
|
|
|
|
|
|
|
|
@example
|
|
|
|
bash ./configure
|
|
|
|
@end example
|
|
|
|
|
|
|
|
@anchor{Darwin}
|
2011-12-12 21:21:24 +01:00
|
|
|
@section Darwin (OS X, iPhone)
|
2011-12-03 21:25:04 +01:00
|
|
|
|
|
|
|
The toolchain provided with Xcode is sufficient to build the basic
|
|
|
|
unacelerated code.
|
|
|
|
|
2011-12-12 21:21:24 +01:00
|
|
|
OS X on PowerPC or ARM (iPhone) requires a preprocessor from
|
2011-12-03 21:25:04 +01:00
|
|
|
@url{http://github.com/yuvi/gas-preprocessor} to build the optimized
|
|
|
|
assembler functions. Just download the Perl script and put it somewhere
|
|
|
|
in your PATH, Libav's configure will pick it up automatically.
|
|
|
|
|
2011-12-12 21:21:24 +01:00
|
|
|
OS X on AMD64 and x86 requires @command{yasm} to build most of the
|
2011-12-03 21:25:04 +01:00
|
|
|
optimized assembler functions @url{http://mxcl.github.com/homebrew/, Homebrew},
|
|
|
|
@url{http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-macos.xml, Gentoo Prefix}
|
|
|
|
or @url{http://www.macports.org, MacPorts} can easily provide it.
|
|
|
|
|
|
|
|
|
|
|
|
@chapter DOS
|
|
|
|
|
|
|
|
Using a cross-compiler is preferred for various reasons.
|
|
|
|
@url{http://www.delorie.com/howto/djgpp/linux-x-djgpp.html}
|
|
|
|
|
|
|
|
|
|
|
|
@chapter OS/2
|
|
|
|
|
|
|
|
For information about compiling Libav on OS/2 see
|
|
|
|
@url{http://www.edm2.com/index.php/FFmpeg}.
|
|
|
|
|
|
|
|
|
|
|
|
@chapter Windows
|
|
|
|
|
2012-09-27 20:39:02 +02:00
|
|
|
@section Native Windows compilation using MinGW or MinGW-w64
|
2011-12-03 21:25:04 +01:00
|
|
|
|
2012-09-27 20:38:59 +02:00
|
|
|
Libav can be built to run natively on Windows using the MinGW or MinGW-w64
|
|
|
|
toolchains. Install the latest versions of MSYS and MinGW or MinGW-w64 from
|
|
|
|
@url{http://www.mingw.org/} or @url{http://mingw-w64.sourceforge.net/}.
|
|
|
|
You can find detailed installation instructions in the download section and
|
|
|
|
the FAQ.
|
2011-12-03 21:25:04 +01:00
|
|
|
|
|
|
|
Notes:
|
|
|
|
|
|
|
|
@itemize
|
|
|
|
|
|
|
|
@item Building natively using MSYS can be sped up by disabling implicit rules
|
|
|
|
in the Makefile by calling @code{make -r} instead of plain @code{make}. This
|
|
|
|
speed up is close to non-existent for normal one-off builds and is only
|
2012-05-10 14:18:10 +02:00
|
|
|
noticeable when running make for a second time (for example during
|
2011-12-03 21:25:04 +01:00
|
|
|
@code{make install}).
|
|
|
|
|
|
|
|
@item In order to compile AVplay, you must have the MinGW development library
|
2012-05-10 14:18:10 +02:00
|
|
|
of @uref{http://www.libsdl.org/, SDL} and @code{pkg-config} installed.
|
2011-12-03 21:25:04 +01:00
|
|
|
|
|
|
|
@item By using @code{./configure --enable-shared} when configuring Libav,
|
2012-05-10 14:18:10 +02:00
|
|
|
you can build all libraries as DLLs.
|
2011-12-03 21:25:04 +01:00
|
|
|
|
|
|
|
@end itemize
|
|
|
|
|
2012-09-27 20:39:02 +02:00
|
|
|
@section Microsoft Visual C++
|
2011-12-03 21:25:04 +01:00
|
|
|
|
2012-09-27 20:39:02 +02:00
|
|
|
Libav can be built with MSVC using a C99-to-C89 conversion utility and
|
2012-10-19 21:12:07 +02:00
|
|
|
wrapper.
|
2011-12-03 21:25:04 +01:00
|
|
|
|
2012-09-27 20:39:02 +02:00
|
|
|
You will need the following prerequisites:
|
2011-12-03 21:25:04 +01:00
|
|
|
|
2012-09-27 20:39:02 +02:00
|
|
|
@itemize
|
|
|
|
@item @uref{https://github.com/rbultje/c99-to-c89/, C99-to-C89 Converter & Wrapper}
|
|
|
|
@item @uref{http://code.google.com/p/msinttypes/, msinttypes}
|
|
|
|
@item @uref{http://www.mingw.org/, MSYS}
|
|
|
|
@item @uref{http://yasm.tortall.net/, YASM}
|
|
|
|
@item @uref{http://gnuwin32.sourceforge.net/packages/bc.htm, bc for Windows} if
|
|
|
|
you want to run @uref{fate.html, FATE}.
|
|
|
|
@end itemize
|
|
|
|
|
|
|
|
To set up a proper MSVC environment in MSYS, you simply need to run
|
|
|
|
@code{msys.bat} from the Visual Studio command prompt.
|
|
|
|
|
2012-10-19 21:12:07 +02:00
|
|
|
Place @code{makedef}, @code{c99wrap.exe}, @code{c99conv.exe}, and @code{yasm.exe}
|
|
|
|
somewhere in your @code{PATH}.
|
2012-09-27 20:39:02 +02:00
|
|
|
|
|
|
|
Next, make sure @code{inttypes.h} and any other headers and libs you want to use
|
|
|
|
are located in a spot that MSVC can see. Do so by modifying the @code{LIB} and
|
|
|
|
@code{INCLUDE} environment variables to include the @strong{Windows} paths to
|
|
|
|
these directories. Alternatively, you can try and use the
|
|
|
|
@code{--extra-cflags}/@code{--extra-ldflags} configure options.
|
|
|
|
|
|
|
|
Finally, run:
|
|
|
|
|
|
|
|
@example
|
|
|
|
./configure --toolchain=msvc
|
|
|
|
make
|
|
|
|
make install
|
|
|
|
@end example
|
|
|
|
|
2012-10-19 21:12:07 +02:00
|
|
|
If you wish to compile static libraries, add @code{--enable-shared} to your
|
|
|
|
configure options. Note that due to the way MSVC handles DLL imports and
|
|
|
|
exports, you cannot compile static and shared libraries at the same time, and
|
|
|
|
enabling shared libraries will automatically disable the static ones.
|
|
|
|
|
2012-09-27 20:39:02 +02:00
|
|
|
Notes:
|
|
|
|
|
|
|
|
@itemize
|
|
|
|
|
2012-10-19 20:19:26 +02:00
|
|
|
@item It is possible that coreutils' @code{link.exe} conflicts with MSVC's linker.
|
|
|
|
You can find out by running @code{which link} to see which @code{link.exe} you
|
|
|
|
are using. If it is located at @code{/bin/link.exe}, then you have the wrong one
|
|
|
|
in your @code{PATH}. Either move or remove that copy, or make sure MSVC's
|
|
|
|
@code{link.exe} takes precedence in your @code{PATH} over coreutils'.
|
|
|
|
|
2012-09-27 20:39:02 +02:00
|
|
|
@item If you wish to build with zlib support, you will have to grab a compatible
|
|
|
|
zlib binary from somewhere, with an MSVC import lib, or if you wish to link
|
|
|
|
statically, you can follow the instructions below to build a compatible
|
|
|
|
@code{zlib.lib} with MSVC. Regardless of which method you use, you must still
|
|
|
|
follow step 3, or compilation will fail.
|
|
|
|
@enumerate
|
|
|
|
@item Grab the @uref{http://zlib.net/, zlib sources}.
|
|
|
|
@item Edit @code{win32/Makefile.msc} so that it uses -MT instead of -MD, since
|
|
|
|
this is how Libav is built as well.
|
|
|
|
@item Edit @code{zconf.h} and remove its inclusion of @code{unistd.h}. This gets
|
|
|
|
erroneously included when building Libav.
|
|
|
|
@item Run @code{nmake -f win32/Makefile.msc}.
|
|
|
|
@item Move @code{zlib.lib}, @code{zconf.h}, and @code{zlib.h} to somewhere MSVC
|
|
|
|
can see.
|
|
|
|
@end enumerate
|
|
|
|
|
|
|
|
@item Libav has been tested with Visual Studio 2010 and 2012, Pro and Express.
|
|
|
|
Anything else is not officially supported.
|
|
|
|
|
|
|
|
@end itemize
|
|
|
|
|
2012-09-28 03:52:34 +02:00
|
|
|
@subsection Linking to Libav with Microsoft Visual C++
|
2012-09-27 20:39:02 +02:00
|
|
|
|
2012-09-28 03:52:34 +02:00
|
|
|
If you plan to link with MSVC-built static libraries, you will need
|
|
|
|
to make sure you have @code{Runtime Library} set to
|
|
|
|
@code{Multi-threaded (/MT)} in your project's settings.
|
2011-12-03 21:25:04 +01:00
|
|
|
|
|
|
|
Libav headers do not declare global data for Windows DLLs through the usual
|
|
|
|
dllexport/dllimport interface. Such data will be exported properly while
|
2012-09-28 03:52:34 +02:00
|
|
|
building, but to use them in your MSVC code you will have to edit the
|
2011-12-03 21:25:04 +01:00
|
|
|
appropriate headers and mark the data as dllimport. For example, in
|
|
|
|
libavutil/pixdesc.h you should have:
|
|
|
|
@example
|
|
|
|
extern __declspec(dllimport) const AVPixFmtDescriptor av_pix_fmt_descriptors[];
|
|
|
|
@end example
|
|
|
|
|
2012-09-28 03:52:34 +02:00
|
|
|
You will also need to define @code{inline} to something MSVC understands:
|
|
|
|
@example
|
|
|
|
#define inline __inline
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Also note, that as stated in @strong{Microsoft Visual C++}, you will need
|
|
|
|
an MSVC-compatible @uref{http://code.google.com/p/msinttypes/, inttypes.h}.
|
|
|
|
|
|
|
|
If you plan on using import libraries created by dlltool, you must
|
|
|
|
set @code{References} to @code{No (/OPT:NOREF)} under the linker optimization
|
|
|
|
settings, otherwise the resulting binaries will fail during runtime.
|
|
|
|
This is not required when using import libraries generated by @code{lib.exe}.
|
2011-12-03 21:25:04 +01:00
|
|
|
This issue is reported upstream at
|
|
|
|
@url{http://sourceware.org/bugzilla/show_bug.cgi?id=12633}.
|
|
|
|
|
|
|
|
To create import libraries that work with the @code{/OPT:REF} option
|
|
|
|
(which is enabled by default in Release mode), follow these steps:
|
|
|
|
|
|
|
|
@enumerate
|
|
|
|
|
2012-09-28 03:52:34 +02:00
|
|
|
@item Open the @emph{Visual Studio Command Prompt}.
|
2011-12-03 21:25:04 +01:00
|
|
|
|
|
|
|
Alternatively, in a normal command line prompt, call @file{vcvars32.bat}
|
|
|
|
which sets up the environment variables for the Visual C++ tools
|
2012-09-28 03:52:34 +02:00
|
|
|
(the standard location for this file is something like
|
|
|
|
@file{C:\Program Files (x86_\Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat}).
|
2011-12-03 21:25:04 +01:00
|
|
|
|
|
|
|
@item Enter the @file{bin} directory where the created LIB and DLL files
|
|
|
|
are stored.
|
|
|
|
|
2012-05-16 19:24:39 +02:00
|
|
|
@item Generate new import libraries with @command{lib.exe}:
|
2011-12-03 21:25:04 +01:00
|
|
|
|
|
|
|
@example
|
2012-05-10 14:18:10 +02:00
|
|
|
lib /machine:i386 /def:..\lib\foo-version.def /out:foo.lib
|
2011-12-03 21:25:04 +01:00
|
|
|
@end example
|
|
|
|
|
2012-05-10 14:18:10 +02:00
|
|
|
Replace @code{foo-version} and @code{foo} with the respective library names.
|
|
|
|
|
2011-12-03 21:25:04 +01:00
|
|
|
@end enumerate
|
|
|
|
|
|
|
|
@anchor{Cross compilation for Windows with Linux}
|
|
|
|
@section Cross compilation for Windows with Linux
|
|
|
|
|
|
|
|
You must use the MinGW cross compilation tools available at
|
|
|
|
@url{http://www.mingw.org/}.
|
|
|
|
|
|
|
|
Then configure Libav with the following options:
|
|
|
|
@example
|
|
|
|
./configure --target-os=mingw32 --cross-prefix=i386-mingw32msvc-
|
|
|
|
@end example
|
|
|
|
(you can change the cross-prefix according to the prefix chosen for the
|
|
|
|
MinGW tools).
|
|
|
|
|
|
|
|
Then you can easily test Libav with @uref{http://www.winehq.com/, Wine}.
|
|
|
|
|
|
|
|
@section Compilation under Cygwin
|
|
|
|
|
|
|
|
Please use Cygwin 1.7.x as the obsolete 1.5.x Cygwin versions lack
|
|
|
|
llrint() in its C library.
|
|
|
|
|
|
|
|
Install your Cygwin with all the "Base" packages, plus the
|
|
|
|
following "Devel" ones:
|
|
|
|
@example
|
|
|
|
binutils, gcc4-core, make, git, mingw-runtime, texi2html
|
|
|
|
@end example
|
|
|
|
|
2012-08-07 14:56:38 +02:00
|
|
|
In order to run FATE you will also need the following "Utils" packages:
|
2011-12-03 21:25:04 +01:00
|
|
|
@example
|
2012-08-07 14:56:38 +02:00
|
|
|
bc, diffutils
|
2011-12-03 21:25:04 +01:00
|
|
|
@end example
|
|
|
|
|
|
|
|
If you want to build Libav with additional libraries, download Cygwin
|
|
|
|
"Devel" packages for Ogg and Vorbis from any Cygwin packages repository:
|
|
|
|
@example
|
|
|
|
libogg-devel, libvorbis-devel
|
|
|
|
@end example
|
|
|
|
|
|
|
|
These library packages are only available from
|
|
|
|
@uref{http://sourceware.org/cygwinports/, Cygwin Ports}:
|
|
|
|
|
|
|
|
@example
|
2012-04-14 14:54:03 +02:00
|
|
|
yasm, libSDL-devel, libfaac-devel, libgsm-devel, libmp3lame-devel,
|
|
|
|
libschroedinger1.0-devel, speex-devel, libtheora-devel, libxvidcore-devel
|
2011-12-03 21:25:04 +01:00
|
|
|
@end example
|
|
|
|
|
2012-05-10 14:18:10 +02:00
|
|
|
The recommendation for x264 is to build it from source, as it evolves too
|
|
|
|
quickly for Cygwin Ports to be up to date.
|
2011-12-03 21:25:04 +01:00
|
|
|
|
|
|
|
@section Crosscompilation for Windows under Cygwin
|
|
|
|
|
|
|
|
With Cygwin you can create Windows binaries that do not need the cygwin1.dll.
|
|
|
|
|
|
|
|
Just install your Cygwin as explained before, plus these additional
|
|
|
|
"Devel" packages:
|
|
|
|
@example
|
|
|
|
gcc-mingw-core, mingw-runtime, mingw-zlib
|
|
|
|
@end example
|
|
|
|
|
|
|
|
and add some special flags to your configure invocation.
|
|
|
|
|
|
|
|
For a static build run
|
|
|
|
@example
|
|
|
|
./configure --target-os=mingw32 --extra-cflags=-mno-cygwin --extra-libs=-mno-cygwin
|
|
|
|
@end example
|
|
|
|
|
|
|
|
and for a build with shared libraries
|
|
|
|
@example
|
|
|
|
./configure --target-os=mingw32 --enable-shared --disable-static --extra-cflags=-mno-cygwin --extra-libs=-mno-cygwin
|
|
|
|
@end example
|
|
|
|
|
|
|
|
@bye
|