You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
406 lines
18 KiB
406 lines
18 KiB
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
|
|
<title>FFmpeg documentation</title>
|
|
<link rel="stylesheet" href="bootstrap.min.css" />
|
|
<link rel="stylesheet" href="style.min.css" />
|
|
|
|
<meta name="description" content="Platform Specific Information: ">
|
|
<meta name="keywords" content="FFmpeg documentation : Platform Specific Information: ">
|
|
<meta name="Generator" content="texi2html 5.0">
|
|
<!-- Created on July 3, 2018 by texi2html 5.0 -->
|
|
<!--
|
|
texi2html was written by:
|
|
Lionel Cons <Lionel.Cons@cern.ch> (original author)
|
|
Karl Berry <karl@freefriends.org>
|
|
Olaf Bachmann <obachman@mathematik.uni-kl.de>
|
|
and many others.
|
|
Maintained by: Many creative people.
|
|
Send bugs and suggestions to <texi2html-bug@nongnu.org>
|
|
|
|
-->
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
</head>
|
|
<body>
|
|
<div class="container">
|
|
|
|
<h1 class="titlefont">Platform Specific Information</h1>
|
|
<hr>
|
|
<a name="SEC_Top"></a>
|
|
|
|
<a name="SEC_Contents"></a>
|
|
<h1>Table of Contents</h1>
|
|
|
|
<div class="contents">
|
|
|
|
<ul class="no-bullet">
|
|
<li><a name="toc-Unix_002dlike" href="#Unix_002dlike">1 Unix-like</a>
|
|
<ul class="no-bullet">
|
|
<li><a name="toc-Advanced-linking-configuration" href="#Advanced-linking-configuration">1.1 Advanced linking configuration</a></li>
|
|
<li><a name="toc-BSD" href="#BSD">1.2 BSD</a></li>
|
|
<li><a name="toc-_0028Open_0029Solaris" href="#g_t_0028Open_0029Solaris">1.3 (Open)Solaris</a></li>
|
|
<li><a name="toc-Darwin-_0028Mac-OS-X_002c-iPhone_0029" href="#Darwin-_0028Mac-OS-X_002c-iPhone_0029">1.4 Darwin (Mac OS X, iPhone)</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-DOS" href="#DOS">2 DOS</a></li>
|
|
<li><a name="toc-OS_002f2" href="#OS_002f2">3 OS/2</a></li>
|
|
<li><a name="toc-Windows" href="#Windows">4 Windows</a>
|
|
<ul class="no-bullet">
|
|
<li><a name="toc-Native-Windows-compilation-using-MinGW-or-MinGW_002dw64" href="#Native-Windows-compilation-using-MinGW-or-MinGW_002dw64">4.1 Native Windows compilation using MinGW or MinGW-w64</a>
|
|
<ul class="no-bullet">
|
|
<li><a name="toc-Native-Windows-compilation-using-MSYS2" href="#Native-Windows-compilation-using-MSYS2">4.1.1 Native Windows compilation using MSYS2</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows" href="#Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows">4.2 Microsoft Visual C++ or Intel C++ Compiler for Windows</a>
|
|
<ul class="no-bullet">
|
|
<li><a name="toc-Linking-to-FFmpeg-with-Microsoft-Visual-C_002b_002b" href="#Linking-to-FFmpeg-with-Microsoft-Visual-C_002b_002b">4.2.1 Linking to FFmpeg with Microsoft Visual C++</a></li>
|
|
</ul></li>
|
|
<li><a name="toc-Cross-compilation-for-Windows-with-Linux-1" href="#Cross-compilation-for-Windows-with-Linux-1">4.3 Cross compilation for Windows with Linux</a></li>
|
|
<li><a name="toc-Compilation-under-Cygwin" href="#Compilation-under-Cygwin">4.4 Compilation under Cygwin</a></li>
|
|
<li><a name="toc-Crosscompilation-for-Windows-under-Cygwin" href="#Crosscompilation-for-Windows-under-Cygwin">4.5 Crosscompilation for Windows under Cygwin</a></li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
|
|
|
|
<hr size="6">
|
|
<a name="Unix_002dlike"></a>
|
|
<h1 class="chapter"><a href="platform.html#toc-Unix_002dlike">1 Unix-like</a></h1>
|
|
|
|
<p>Some parts of FFmpeg 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:
|
|
</p>
|
|
<div class="example">
|
|
<pre class="example">$(gcc -print-prog-name=as) --version
|
|
</pre></div>
|
|
|
|
<p>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</code>
|
|
to configure.
|
|
</p>
|
|
<a name="Advanced-linking-configuration"></a>
|
|
<h2 class="section"><a href="platform.html#toc-Advanced-linking-configuration">1.1 Advanced linking configuration</a></h2>
|
|
|
|
<p>If you compiled FFmpeg libraries statically and you want to use them to
|
|
build your own shared library, you may need to force PIC support (with
|
|
<code>--enable-pic</code> during FFmpeg configure) and add the following option
|
|
to your project LDFLAGS:
|
|
</p>
|
|
<div class="example">
|
|
<pre class="example">-Wl,-Bsymbolic
|
|
</pre></div>
|
|
|
|
<p>If your target platform requires position independent binaries, you should
|
|
pass the correct linking flag (e.g. <code>-pie</code>) to <code>--extra-ldexeflags</code>.
|
|
</p>
|
|
<a name="BSD"></a>
|
|
<h2 class="section"><a href="platform.html#toc-BSD">1.2 BSD</a></h2>
|
|
|
|
<p>BSD make will not build FFmpeg, you need to install and use GNU Make
|
|
(<code>gmake</code>).
|
|
</p>
|
|
<a name="g_t_0028Open_0029Solaris"></a>
|
|
<h2 class="section"><a href="platform.html#toc-_0028Open_0029Solaris">1.3 (Open)Solaris</a></h2>
|
|
|
|
<p>GNU Make is required to build FFmpeg, so you have to invoke (<code>gmake</code>),
|
|
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</code>
|
|
or <code>--extra-libs=/usr/lib/64/values-xpg6.o</code> 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:
|
|
</p>
|
|
<div class="example">
|
|
<pre class="example">bash ./configure
|
|
</pre></div>
|
|
|
|
<p><a name="Darwin"></a>
|
|
</p><a name="Darwin-_0028Mac-OS-X_002c-iPhone_0029"></a>
|
|
<h2 class="section"><a href="platform.html#toc-Darwin-_0028Mac-OS-X_002c-iPhone_0029">1.4 Darwin (Mac OS X, iPhone)</a></h2>
|
|
|
|
<p>The toolchain provided with Xcode is sufficient to build the basic
|
|
unaccelerated code.
|
|
</p>
|
|
<p>Mac OS X on PowerPC or ARM (iPhone) requires a preprocessor from
|
|
<a href="https://github.com/FFmpeg/gas-preprocessor">https://github.com/FFmpeg/gas-preprocessor</a> or
|
|
<a href="https://github.com/yuvi/gas-preprocessor">https://github.com/yuvi/gas-preprocessor</a>(currently outdated) to build the optimized
|
|
assembly functions. Put the Perl script somewhere
|
|
in your PATH, FFmpeg’s configure will pick it up automatically.
|
|
</p>
|
|
<p>Mac OS X on amd64 and x86 requires <code>nasm</code> to build most of the
|
|
optimized assembly functions. <a href="http://www.finkproject.org/">Fink</a>,
|
|
<a href="https://wiki.gentoo.org/wiki/Project:Prefix">Gentoo Prefix</a>,
|
|
<a href="https://mxcl.github.com/homebrew/">Homebrew</a>
|
|
or <a href="http://www.macports.org">MacPorts</a> can easily provide it.
|
|
</p>
|
|
|
|
<a name="DOS"></a>
|
|
<h1 class="chapter"><a href="platform.html#toc-DOS">2 DOS</a></h1>
|
|
|
|
<p>Using a cross-compiler is preferred for various reasons.
|
|
<a href="http://www.delorie.com/howto/djgpp/linux-x-djgpp.html">http://www.delorie.com/howto/djgpp/linux-x-djgpp.html</a>
|
|
</p>
|
|
|
|
<a name="OS_002f2"></a>
|
|
<h1 class="chapter"><a href="platform.html#toc-OS_002f2">3 OS/2</a></h1>
|
|
|
|
<p>For information about compiling FFmpeg on OS/2 see
|
|
<a href="http://www.edm2.com/index.php/FFmpeg">http://www.edm2.com/index.php/FFmpeg</a>.
|
|
</p>
|
|
|
|
<a name="Windows"></a>
|
|
<h1 class="chapter"><a href="platform.html#toc-Windows">4 Windows</a></h1>
|
|
|
|
<p>To get help and instructions for building FFmpeg under Windows, check out
|
|
the FFmpeg Windows Help Forum at <a href="http://ffmpeg.zeranoe.com/forum/">http://ffmpeg.zeranoe.com/forum/</a>.
|
|
</p>
|
|
<a name="Native-Windows-compilation-using-MinGW-or-MinGW_002dw64"></a>
|
|
<h2 class="section"><a href="platform.html#toc-Native-Windows-compilation-using-MinGW-or-MinGW_002dw64">4.1 Native Windows compilation using MinGW or MinGW-w64</a></h2>
|
|
|
|
<p>FFmpeg can be built to run natively on Windows using the MinGW-w64
|
|
toolchain. Install the latest versions of MSYS2 and MinGW-w64 from
|
|
<a href="http://msys2.github.io/">http://msys2.github.io/</a> and/or <a href="http://mingw-w64.sourceforge.net/">http://mingw-w64.sourceforge.net/</a>.
|
|
You can find detailed installation instructions in the download section and
|
|
the FAQ.
|
|
</p>
|
|
<p>Notes:
|
|
</p>
|
|
<ul>
|
|
<li> Building for the MSYS environment is discouraged, MSYS2 provides a full
|
|
MinGW-w64 environment through ‘<tt>mingw64_shell.bat</tt>’ or
|
|
‘<tt>mingw32_shell.bat</tt>’ that should be used instead of the environment
|
|
provided by ‘<tt>msys2_shell.bat</tt>’.
|
|
|
|
</li><li> Building using MSYS2 can be sped up by disabling implicit rules in the
|
|
Makefile by calling <code>make -r</code> instead of plain <code>make</code>. This
|
|
speed up is close to non-existent for normal one-off builds and is only
|
|
noticeable when running make for a second time (for example during
|
|
<code>make install</code>).
|
|
|
|
</li><li> In order to compile FFplay, you must have the MinGW development library
|
|
of <a href="http://www.libsdl.org/">SDL</a> and <code>pkg-config</code> installed.
|
|
|
|
</li><li> By using <code>./configure --enable-shared</code> when configuring FFmpeg,
|
|
you can build the FFmpeg libraries (e.g. libavutil, libavcodec,
|
|
libavformat) as DLLs.
|
|
|
|
</li></ul>
|
|
|
|
<a name="Native-Windows-compilation-using-MSYS2"></a>
|
|
<h3 class="subsection"><a href="platform.html#toc-Native-Windows-compilation-using-MSYS2">4.1.1 Native Windows compilation using MSYS2</a></h3>
|
|
|
|
<p>The MSYS2 MinGW-w64 environment provides ready to use toolchains and dependencies
|
|
through <code>pacman</code>.
|
|
</p>
|
|
<p>Make sure to use ‘<tt>mingw64_shell.bat</tt>’ or ‘<tt>mingw32_shell.bat</tt>’ to have
|
|
the correct MinGW-w64 environment. The default install provides shortcuts to
|
|
them under <code>MinGW-w64 Win64 Shell</code> and <code>MinGW-w64 Win32 Shell</code>.
|
|
</p>
|
|
<div class="example">
|
|
<pre class="example"># normal msys2 packages
|
|
pacman -S make pkgconf diffutils
|
|
|
|
# mingw-w64 packages and toolchains
|
|
pacman -S mingw-w64-x86_64-nasm mingw-w64-x86_64-gcc mingw-w64-x86_64-SDL2
|
|
</pre></div>
|
|
|
|
<p>To target 32 bits replace <code>x86_64</code> with <code>i686</code> in the command above.
|
|
</p>
|
|
<a name="Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows"></a>
|
|
<h2 class="section"><a href="platform.html#toc-Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows">4.2 Microsoft Visual C++ or Intel C++ Compiler for Windows</a></h2>
|
|
|
|
<p>FFmpeg can be built with MSVC 2013 or later.
|
|
</p>
|
|
<p>You will need the following prerequisites:
|
|
</p>
|
|
<ul>
|
|
<li> <a href="http://msys2.github.io/">MSYS2</a>
|
|
</li><li> <a href="http://www.nasm.us/">NASM</a>
|
|
(Also available via MSYS2’s package manager.)
|
|
</li></ul>
|
|
|
|
<p>To set up a proper environment in MSYS2, you need to run <code>msys_shell.bat</code> from
|
|
the Visual Studio or Intel Compiler command prompt.
|
|
</p>
|
|
<p>Place <code>yasm.exe</code> somewhere in your <code>PATH</code>.
|
|
</p>
|
|
<p>Next, make sure any other headers and libs you want to use, such as zlib, are
|
|
located in a spot that the compiler can see. Do so by modifying the <code>LIB</code>
|
|
and <code>INCLUDE</code> environment variables to include the <strong>Windows-style</strong>
|
|
paths to these directories. Alternatively, you can try to use the
|
|
<code>--extra-cflags</code>/<code>--extra-ldflags</code> configure options.
|
|
</p>
|
|
<p>Finally, run:
|
|
</p>
|
|
<div class="example">
|
|
<pre class="example">For MSVC:
|
|
./configure --toolchain=msvc
|
|
|
|
For ICL:
|
|
./configure --toolchain=icl
|
|
|
|
make
|
|
make install
|
|
</pre></div>
|
|
|
|
<p>If you wish to compile shared libraries, add <code>--enable-shared</code> to your
|
|
configure options. Note that due to the way MSVC and ICL handle 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.
|
|
</p>
|
|
<p>Notes:
|
|
</p>
|
|
<ul>
|
|
<li> 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</code> with MSVC. Regardless of which method you use, you must still
|
|
follow step 3, or compilation will fail.
|
|
<ol>
|
|
<li> Grab the <a href="http://zlib.net/">zlib sources</a>.
|
|
</li><li> Edit <code>win32/Makefile.msc</code> so that it uses -MT instead of -MD, since
|
|
this is how FFmpeg is built as well.
|
|
</li><li> Edit <code>zconf.h</code> and remove its inclusion of <code>unistd.h</code>. This gets
|
|
erroneously included when building FFmpeg.
|
|
</li><li> Run <code>nmake -f win32/Makefile.msc</code>.
|
|
</li><li> Move <code>zlib.lib</code>, <code>zconf.h</code>, and <code>zlib.h</code> to somewhere MSVC
|
|
can see.
|
|
</li></ol>
|
|
|
|
</li><li> FFmpeg has been tested with the following on i686 and x86_64:
|
|
<ul>
|
|
<li> Visual Studio 2013 Pro and Express
|
|
</li><li> Intel Composer XE 2013
|
|
</li><li> Intel Composer XE 2013 SP1
|
|
</li></ul>
|
|
<p>Anything else is not officially supported.
|
|
</p>
|
|
</li></ul>
|
|
|
|
<a name="Linking-to-FFmpeg-with-Microsoft-Visual-C_002b_002b"></a>
|
|
<h3 class="subsection"><a href="platform.html#toc-Linking-to-FFmpeg-with-Microsoft-Visual-C_002b_002b">4.2.1 Linking to FFmpeg with Microsoft Visual C++</a></h3>
|
|
|
|
<p>If you plan to link with MSVC-built static libraries, you will need
|
|
to make sure you have <code>Runtime Library</code> set to
|
|
<code>Multi-threaded (/MT)</code> in your project’s settings.
|
|
</p>
|
|
<p>You will need to define <code>inline</code> to something MSVC understands:
|
|
</p><div class="example">
|
|
<pre class="example">#define inline __inline
|
|
</pre></div>
|
|
|
|
<p>Also note, that as stated in <strong>Microsoft Visual C++</strong>, you will need
|
|
an MSVC-compatible <a href="http://code.google.com/p/msinttypes/">inttypes.h</a>.
|
|
</p>
|
|
<p>If you plan on using import libraries created by dlltool, you must
|
|
set <code>References</code> to <code>No (/OPT:NOREF)</code> 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</code>.
|
|
This issue is reported upstream at
|
|
<a href="http://sourceware.org/bugzilla/show_bug.cgi?id=12633">http://sourceware.org/bugzilla/show_bug.cgi?id=12633</a>.
|
|
</p>
|
|
<p>To create import libraries that work with the <code>/OPT:REF</code> option
|
|
(which is enabled by default in Release mode), follow these steps:
|
|
</p>
|
|
<ol>
|
|
<li> Open the <em>Visual Studio Command Prompt</em>.
|
|
|
|
<p>Alternatively, in a normal command line prompt, call ‘<tt>vcvars32.bat</tt>’
|
|
which sets up the environment variables for the Visual C++ tools
|
|
(the standard location for this file is something like
|
|
‘<tt>C:\Program Files (x86_\Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat</tt>’).
|
|
</p>
|
|
</li><li> Enter the ‘<tt>bin</tt>’ directory where the created LIB and DLL files
|
|
are stored.
|
|
|
|
</li><li> Generate new import libraries with <code>lib.exe</code>:
|
|
|
|
<div class="example">
|
|
<pre class="example">lib /machine:i386 /def:..\lib\foo-version.def /out:foo.lib
|
|
</pre></div>
|
|
|
|
<p>Replace <code>foo-version</code> and <code>foo</code> with the respective library names.
|
|
</p>
|
|
</li></ol>
|
|
|
|
<p><a name="Cross-compilation-for-Windows-with-Linux"></a>
|
|
</p><a name="Cross-compilation-for-Windows-with-Linux-1"></a>
|
|
<h2 class="section"><a href="platform.html#toc-Cross-compilation-for-Windows-with-Linux-1">4.3 Cross compilation for Windows with Linux</a></h2>
|
|
|
|
<p>You must use the MinGW cross compilation tools available at
|
|
<a href="http://www.mingw.org/">http://www.mingw.org/</a>.
|
|
</p>
|
|
<p>Then configure FFmpeg with the following options:
|
|
</p><div class="example">
|
|
<pre class="example">./configure --target-os=mingw32 --cross-prefix=i386-mingw32msvc-
|
|
</pre></div>
|
|
<p>(you can change the cross-prefix according to the prefix chosen for the
|
|
MinGW tools).
|
|
</p>
|
|
<p>Then you can easily test FFmpeg with <a href="http://www.winehq.com/">Wine</a>.
|
|
</p>
|
|
<a name="Compilation-under-Cygwin"></a>
|
|
<h2 class="section"><a href="platform.html#toc-Compilation-under-Cygwin">4.4 Compilation under Cygwin</a></h2>
|
|
|
|
<p>Please use Cygwin 1.7.x as the obsolete 1.5.x Cygwin versions lack
|
|
llrint() in its C library.
|
|
</p>
|
|
<p>Install your Cygwin with all the "Base" packages, plus the
|
|
following "Devel" ones:
|
|
</p><div class="example">
|
|
<pre class="example">binutils, gcc4-core, make, git, mingw-runtime, texinfo
|
|
</pre></div>
|
|
|
|
<p>In order to run FATE you will also need the following "Utils" packages:
|
|
</p><div class="example">
|
|
<pre class="example">diffutils
|
|
</pre></div>
|
|
|
|
<p>If you want to build FFmpeg with additional libraries, download Cygwin
|
|
"Devel" packages for Ogg and Vorbis from any Cygwin packages repository:
|
|
</p><div class="example">
|
|
<pre class="example">libogg-devel, libvorbis-devel
|
|
</pre></div>
|
|
|
|
<p>These library packages are only available from
|
|
<a href="http://sourceware.org/cygwinports/">Cygwin Ports</a>:
|
|
</p>
|
|
<div class="example">
|
|
<pre class="example">yasm, libSDL-devel, libgsm-devel, libmp3lame-devel,
|
|
speex-devel, libtheora-devel, libxvidcore-devel
|
|
</pre></div>
|
|
|
|
<p>The recommendation for x264 is to build it from source, as it evolves too
|
|
quickly for Cygwin Ports to be up to date.
|
|
</p>
|
|
<a name="Crosscompilation-for-Windows-under-Cygwin"></a>
|
|
<h2 class="section"><a href="platform.html#toc-Crosscompilation-for-Windows-under-Cygwin">4.5 Crosscompilation for Windows under Cygwin</a></h2>
|
|
|
|
<p>With Cygwin you can create Windows binaries that do not need the cygwin1.dll.
|
|
</p>
|
|
<p>Just install your Cygwin as explained before, plus these additional
|
|
"Devel" packages:
|
|
</p><div class="example">
|
|
<pre class="example">gcc-mingw-core, mingw-runtime, mingw-zlib
|
|
</pre></div>
|
|
|
|
<p>and add some special flags to your configure invocation.
|
|
</p>
|
|
<p>For a static build run
|
|
</p><div class="example">
|
|
<pre class="example">./configure --target-os=mingw32 --extra-cflags=-mno-cygwin --extra-libs=-mno-cygwin
|
|
</pre></div>
|
|
|
|
<p>and for a build with shared libraries
|
|
</p><div class="example">
|
|
<pre class="example">./configure --target-os=mingw32 --enable-shared --disable-static --extra-cflags=-mno-cygwin --extra-libs=-mno-cygwin
|
|
</pre></div>
|
|
|
|
</div>
|
|
</body>
|
|
</html>
|
|
|
|
|