[Bug 773114] meson: fixes for windows build

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=773114

--- Comment #44 from Scott D Phillips <scott.d.phillips at intel.com> ---
(In reply to Nirbheek Chauhan from comment #43)
> Note that we might also want to look into updating glib to define G_OS_WIN32
> on MSYS2 if it's appropriate since we've been looking at updating Cerbero on
> Windows to use MSYS2. Could you look into that please, Scott?

An msys2 setup has a few repositories it can install packages from:

> $ pacman -Ss gcc
> mingw32/mingw-w64-i686-gcc 6.2.0-2 (mingw-w64-i686-toolchain)
>     GNU Compiler Collection (C,C++,OpenMP) for MinGW-w64
> mingw64/mingw-w64-x86_64-gcc 6.2.0-2 (mingw-w64-x86_64-toolchain)
>     GNU Compiler Collection (C,C++,OpenMP) for MinGW-w64
> msys/gcc 5.3.0-3 (msys2-devel)
>     The GNU Compiler Collection - C and C++ frontends

msys/gcc is a cygwin type toolchain that will simulate some unix stuff and if
you install msys/glib2 it will have G_OS_UNIX set. mingw64/...-gcc doesn't
include that unix emulation layer so mingw64/...-glib will have G_OS_WIN32 set.
Really the absence of G_OS_UNIX is more important than the presence of
G_OS_WIN32 meaning that some unixy stuff is unavailable. And then
G_PLATFORM_WIN32 is set in both msys/glib2 and mingw64/...-glib and windows API
calls are available from both corresponding toolchains.

I think the cerbero build currently uses the mingw64 toolchain currently, so an
msys2 based cerbero would probably just have `pacman -S mingw64/...` and then
not need any other changes related to G_OS_WIN32.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.