[FFmpeg-devel] [PATCH] configure: support MSYS2
h.leppkes at gmail.com
Sun Jan 25 18:47:01 CET 2015
On Sun, Jan 25, 2015 at 6:43 PM, Michael Niedermayer <michaelni at gmx.at>
> On Sun, Jan 25, 2015 at 05:02:58PM +0100, Reimar Döffinger wrote:
> > On Sun, Jan 25, 2015 at 03:59:12PM +0100, Hendrik Leppkes wrote:
> > > On Sun, Jan 25, 2015 at 3:26 PM, Hendrik Leppkes <h.leppkes at gmail.com>
> > > wrote:
> > >
> > > > MSYS2 uses a system name of "MSYS_NT-6.3" instead of
> "MINGW32_NT-6.3" in
> > > > MSYS1.
> > > >
> > >
> > > Apparently this isn't quite correct, and you have to start MSYS2 with a
> > > special batch file that overrides this for you.
> > > Just running bash.exe or sh.exe from a DOS prompt results in this and
> > > apparently considered "wrong usage".
> > I don't really see anything wrong with this, however I'd rather have
> > a compiler-based detection.
> > I.e. if the compiler define __MINGW32__ set the host to mingw (unless
> > set explicitly).
> > This should also address my other annoyance that you have to specify
> > --host when it really should be obvious that you are cross-compiling to
> > MINGW for example.
> i dont use "--host*" for my mingw building
> just -cc='ccache x86_64-w64-mingw32-gcc' --arch=x86_64 --target-os=mingw32
> --cross-prefix=x86_64-w64-mingw32- --target_exec=wine
> the rest i use should not be mingw specific
I've never had to specify --host things either, the only problem with MSYS2
I ran into was that you still need to specify --target-os unless you use
their fancy batch file, and that tripped me up a bit.
Never a problem with old MSYS and my own gcc build.
More information about the ffmpeg-devel