On Mon, Jan 19, 2015 at 1:32 PM, Michael Niedermayer <michae...@gmx.at> wrote:
> On Mon, Jan 19, 2015 at 07:43:41AM +0100, Reimar Döffinger wrote: > > On 19.01.2015, at 03:05, Michael Niedermayer <michae...@gmx.at> wrote: > > > On Thu, Jan 01, 2015 at 10:00:25AM +0100, Reimar Döffinger wrote: > > >> Useful to select e.g. between mingw32, 32-bit mingw64 and 64-bit > mingw64 > > >> toolchains, which all are not cross-compilation toolchains. > > >> > > >> Signed-off-by: Reimar Döffinger <reimar.doeffin...@gmx.de> > > > > > > is this intended for building with mingw* on windows ? > > > if so it should be ok > > > the patch just confused me a bit as i build with mingw64 (32&64bit) > > > just fine on linux without any of this > > > > Yes, but you have to specify --arch and --target-os, and not sure if > disabling runtime-cpudetection would work etc. > > > > It's even more annoying if you want to compile for 32 bit on a 64 bit > system (you can use -m32 at least in some cases, but this seems simpler and > more consistent). > > hmm > at least ubuntu has seperate packages for 32 and 64bit > gcc-mingw-w64-i686 and gcc-mingw-w64-x86-64 > so building for the 32bit variant is just like cross compiling to > any other target > Thats how my toolchain is setup on Windows as well, so i just use "--cross-prefix=x86_64-w64-mingw32-" when building for x86_64. Note sure what this patch would improve there, I guess allowing the host tools to also be built with the 64-bit compiler, but meh? :) - Hendrik _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
