Mingw(32) is rather poorly maintaned and has quite a lot of bugs. And
because our Windows cross builds were also poorly maintained and most of
the cross-tests were broken as well, I'm just taking this step and try
to switch to mingw-w64 for everything "cross Windows".
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Especially for the 64bit mingw target, because libgcrypt contains
protected mode assembly.
Also, this adds gettext to the crossAttrs of libgpg-error, because it
tries to regenerate the MO files.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This is to make sure that we don't get Xlibs or alsa in cross builds,
because those aren't available on non-Linux/Unix platforms.
Also, until we don't have the DirectX SDK packaged, let's disable it
during cross builds.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This also cleans up the package expression a bit and we no longer
directly override the phases (except patchPhase).
Also for cross-builds we're using the stock mingw target and pass CC, LD
and STRIP to make, because the mingw-w64 targets of the upstream package
are outdated.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
In Windows there is no get(e)uid() call available, so the build fails.
The patch now checks whether OPENSSL_SYS_WINDOWS is defined and only
uses those calls if _not_ on Windows.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This requires recent versions of aqbanking and gwenhywfar:
https://devel.aqbanking.de/trac/aqbanking/ticket/197
It seems as if the developers have changed their version numbering
scheme in 2012 and have only released versions with the "beta" suffix
since then.
This reverts commit 32a4081a7f.
After ec985c8ff the apps linked to 2.11 fontconfig run fine on nixos
with older /etc/fonts/, but the other way won't work.
Unfortunately, I see no easy work-around ATM.