Changes between Version 9 and Version 10 of CompilationGuide/CrossCompilingForWindows

Timestamp:

Nov 1, 2017, 2:01:33 PM (9 years ago)

Author:

slhck

Comment:

add prominent link to GitHub cross-compile script, as guide seems quite outdated / incomplete

CompilationGuide/CrossCompilingForWindows

@@ -1 @@
-= Intro =
+= Cross Compiling for Windows =
 
-Basically, cross compiling FFmpeg for windows means that you use a special version of the gcc compiler (and related tools) that output a working windows executable when they're done.  You can copy it to your windows box and then use it (or use wine to run it under linux, but that kind of defeats the point).
+[[PageOutline(2, Contents)]]
 
-This is sometimes easier than using a "native" compilation in windows because some dependencies' configure scripts accept a cross compiler more readily than a native windows mingw gcc, etc.  It also may be "faster" than using mingw's gcc in windows, for whatever reason gcc seems faster in linux.
+== Introduction ==
 
-Most cross compilation are done under Linux, but it is possible to us OS X as a host machine as well.
+Cross compiling FFmpeg for Windows means that you use a special version of the `gcc` compiler (and related tools) that output a working Windows executable when they're done. You can copy it to your Windows box and then use it (or use WINE to run it under Linux, but that kind of defeats the point).
 
-Also "windows 10 bash" can do cross compilation as well.
+Most cross compilation is done under Linux, but it is possible to use macOS as a host machine as well. Windows 10 WSL can do cross compilation as well.
 
-= Automated cross compiling environment =
+Note that cross-compiling is sometimes easier than using a "native" compilation under Windows because some dependencies' configure scripts accept a cross compiler more readily than a native Windows MinGW, `gcc`, etc. It also may be "faster" than using `gcc` under Windows.
+
+{{{
+#!div style="border: 1px solid #c7e5c7; margin: 1em; background-color: #ddffdd;"
+'''Tip:''' The [https://github.com/rdp/ffmpeg-windows-build-helpers FFmpeg Windows Build Helpers] script can automatically cross-compile FFmpeg for Windows. You can still follow this guide if you want to manually compile FFmpeg.
+}}}
+
+== Cross-Compiling Environment ==
+
+=== Automated Cross Compiling Environment ===
 
 Some building environments aim to automatically build the cross compilers and dependencies of FFmpeg. By using these projects you can eliminate the mess of building toolchains yourself. These projects include [http://mxe.cc MXE] and [http://win-builds.org Win-builds].
 
 MXE is more feature-complete as of Dec 2013, as
+
 * it has more dependencies for FFmpeg (x264, xvid, etc.)
-* it has a ffmpeg package (by default it is libraries-only, but users are able to generate the programs to by simply deleting one line in the building recipe)
-* it supports OS X as a host machine
+* it has an ffmpeg package (by default it is libraries-only, but users are able to generate the programs to by simply deleting one line in the building recipe)
+* it supports macOS as a host machine
 * it supports MinGW in addition to mingw-w64.
 
-Win-builds as the official package manager for mingw-w64, is really new, and it does not have as many multimedia packages as MXE.
+Win-builds as the official package manager for mingw-w64 is really new, and it does not have as many multimedia packages as MXE.
 
-= Cross Compiler =
+=== Linux Packages ===
 
-Zeranoe has a [http://ffmpeg.zeranoe.com/blog/ script] for compiling your own windows cross compiler, then you can use it to [http://ffmpeg.zeranoe.com/forum/viewtopic.php?f=19&t=459 compile ffmpeg and its libs].  NB that it can be a little tricky, you could try using [https://github.com/rdp/ffmpeg-windows-build-helpers this script] which attempts to automated building the cross compiler and gcc.
+Some Linux distros have packages like `mingw-w64-dev` or `gcc-mingw-w64-i686` which might also get a working local cross compiler system.  They'll add `x86_64-w64-mingw32-gcc` to your `PATH` and you're ready to go.
 
-Another option is that some linux distros have packages like mingw-w64-dev or gcc-mingw-w64-i686 which might also get a working local cross compiler system.  Basically, they'll add x86_64-w64-mingw32-gcc to a directory or to the PATH somehow.  And you're ready to go.
 
-= Compile dependencies =
+== Compile FFmpeg ==
 
-Next cross compile any added dependencies you may want, for instead libx264.
+Now configure and compile FFmpeg like:
 
-The script "cross_compile_ffmpeg.sh" in [https://github.com/rdp/ffmpeg-windows-build-helpers this repository] lists many dependencies.
-
-= Compile FFmpeg =
-
-Now basically configure and compile FFmpeg like 
 {{{
-$ ./configure --arch=x86 --target-os=mingw32 --cross-prefix=i686-w64-mingw32- --pkg-config=pkg-config
-$ make
+./configure --arch=x86 --target-os=mingw32 --cross-prefix=i686-w64-mingw32-
+make
 }}}
 
-and other options if you want them, like --enable-libx264, etc.
+and other options if you want them, like `--enable-libx264`, etc. if you have these dependencies cross-compiled as well.
 
-This should eventually create the file ffmpeg_g.exe (ffmpeg.exe with debug symbols) and ffmpeg.exe (ffmpeg.exe "stripped" of its debug symbols).  If you cross compile SDL before hand, it will also include ffplay.exe
+This should eventually create the file `ffmpeg_g.exe` (`ffmpeg.exe` with debug symbols) and `ffmpeg.exe` (`ffmpeg.exe` "stripped" of its debug symbols).  If you cross compile SDL beforehand, it will also include `ffplay.exe`.
 
-= Resources =
-
-[https://github.com/rdp/ffmpeg-windows-build-helpers This repository] has a script that compiles the cross compiler locally
+== Getting Help ==
 
 You can ask questions on the [http://ffmpeg.zeranoe.com/forum/ Zeranoe Forum].