Comments on: FFmpeg & cross-compiling for Windows on Linux http://www.plutinosoft.com/ffmpeg-cross-compiling-for-windows-on-linux Sun, 05 Sep 2010 18:33:39 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: roboknight http://www.plutinosoft.com/ffmpeg-cross-compiling-for-windows-on-linux/comment-page-1#comment-17779 roboknight Thu, 15 Apr 2010 21:29:02 +0000 http://www.plutinosoft.com/blog/?p=534#comment-17779 Oh, one quick note to my previous post: all the dashes before options are doubled. This blog doesn't register them unless you do something like quoting your text or something, I'd guess. Didn't notice that when I was doing this, but I think a previous poster mentioned it also. Oh, one quick note to my previous post: all the dashes before options are doubled. This blog doesn’t register them unless you do something like quoting your text or something, I’d guess. Didn’t notice that when I was doing this, but I think a previous poster mentioned it also.

]]> By: roboknight http://www.plutinosoft.com/ffmpeg-cross-compiling-for-windows-on-linux/comment-page-1#comment-17778 roboknight Thu, 15 Apr 2010 21:27:00 +0000 http://www.plutinosoft.com/blog/?p=534#comment-17778 This is how I got cross compiling to work (from a mac to pc ... how's that for a cross). First, I built the mingw32 tools for the Mac. I won't go into that. It was long and painful, plus, if you are using linux, apt or yum or another package manager will go a long way to helping you get the tools. Second, I got ffmpeg from source using git: git clone git://git.ffmpeg.org/ffmpeg/ cd ffmpeg git clone git://git.ffmpeg.org/libswscale/ Once that was accomplished, I built a build directory: mkdir build cd build Then I used this configure line: ../configure --cross-prefix=/Users/bpw/WindowsTools/bin/i386-mingw32- --enable-cross-compile --arch=i386 --target-os=mingw32 --enable-memalign-hack Make sure when you use this that GCC_EXEC_PREFIX is unset or pointing to the location of your crt1.o file in your tools installation. In general though, having this set can cause a lot of inadvertent "non-configures". Also note that the the --cross-prefix _includes_ the i386-mingw32- . You need to use _YOUR PREFIX_. There are probably a few other ways to provide the prefix, but this one is the easiest. Also, make sure your path points to your tools. At any rate, most of this is trivial information for people who cross-compile on a regular basis, but I discovered there is a lot of outdated info on cross-compiling ffmpeg (options that don't exist anymore, options that have changed, new options). At any rate, this got me building. I tested ffmpeg on WindowsXP running under VirtualBox and it seemed to work great. I need to test it a little more heavily before I give it the final okay, but it at least built. I'm building on a Macbook Pro, so I think there might be some 64 bit issues, but maybe I won't run into them because I'm going to a 32 bit target. At least I hope not. This is how I got cross compiling to work (from a mac to pc … how’s that for a cross).
First, I built the mingw32 tools for the Mac. I won’t go into that. It was long and painful, plus, if you are using linux, apt or yum or another package manager will go a long way to helping you get the tools.

Second, I got ffmpeg from source using git:

git clone git://git.ffmpeg.org/ffmpeg/
cd ffmpeg
git clone git://git.ffmpeg.org/libswscale/

Once that was accomplished, I built a build directory:

mkdir build
cd build

Then I used this configure line:
../configure –cross-prefix=/Users/bpw/WindowsTools/bin/i386-mingw32- –enable-cross-compile –arch=i386 –target-os=mingw32 –enable-memalign-hack

Make sure when you use this that GCC_EXEC_PREFIX is unset or pointing to the location of your crt1.o file in your tools installation. In general though, having this set can cause a lot of inadvertent “non-configures”. Also note that the the –cross-prefix _includes_ the i386-mingw32- . You need to use _YOUR PREFIX_. There are probably a few other ways to provide the prefix, but this one is the easiest. Also, make sure your path points to your tools.

At any rate, most of this is trivial information for people who cross-compile on a regular basis, but I discovered there is a lot of outdated info on cross-compiling ffmpeg (options that don’t exist anymore, options that have changed, new options). At any rate, this got me building. I tested ffmpeg on WindowsXP running under VirtualBox and it seemed to work great. I need to test it a little more heavily before I give it the final okay, but it at least built. I’m building on a Macbook Pro, so I think there might be some 64 bit issues, but maybe I won’t run into them because I’m going to a 32 bit target. At least I hope not.

]]>