From: aeadio <aeadio@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] wine: Use MinGW to build WinPE DLLs
Date: Tue, 05 Jan 2021 05:54:54 +0100 [thread overview]
Message-ID: <20210105045454.m1m8j-kCdk0U1UR3PKHWfh4apHODzPdwxZ0qHcxx5IE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27678@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
There is an updated pull request by aeadio against master on the void-packages repository
https://github.com/aeadio/void-packages wine-mingw
https://github.com/void-linux/void-packages/pull/27678
wine: Use MinGW to build WinPE DLLs
As of 5.x, Wine can now build DLLs in native WinPE format if the MinGW cross compiler is present. This is needed for some newer games to pass DRM/anti-cheat checks that validate the integrity of loaded system libraries.
See:
https://www.winehq.org/announce/5.0
https://bugs.winehq.org/show_bug.cgi?id=45349
I've split this out into a build option that's enabled by default.
This was built and tested on an x86_64 host, with 32-bit Wine tested as well. Games which would not launch on Void's Wine build are now functioning with this change (namely, World of Warcraft).
A patch file from https://github.com/void-linux/void-packages/pull/27678.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-wine-mingw-27678.patch --]
[-- Type: text/x-diff, Size: 1465 bytes --]
From aff1d8705038997051af6d560794b52c3f1264df Mon Sep 17 00:00:00 2001
From: Anthony Eadicicco <a@aead.io>
Date: Mon, 4 Jan 2021 23:28:45 -0500
Subject: [PATCH] wine: Use MinGW to build WinPE DLLs
---
srcpkgs/wine/template | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/wine/template b/srcpkgs/wine/template
index 0e6629f4c3e..fd03474eba9 100644
--- a/srcpkgs/wine/template
+++ b/srcpkgs/wine/template
@@ -1,7 +1,7 @@
# Template file for 'wine'
pkgname=wine
version=6.0rc5
-revision=1
+revision=2
wrksrc=wine-${version/r/-r}
build_style=gnu-configure
configure_args="--bindir=/usr/libexec/wine"
@@ -12,6 +12,10 @@ homepage="http://www.winehq.org/"
distfiles="https://dl.winehq.org/wine/source/${version%r*}/wine-${version/r/-r}.tar.xz"
checksum=f1f10a0aef4dcc9cf4ec67f0828fc1f7f364e2e8e7c2f027c253c8e2004bf451
+build_options="mingw"
+build_options_default="mingw"
+desc_option_mingw="Use the MinGW cross compiler to build WinPE DLLs"
+
lib32mode=full
archs="i686* x86_64*"
@@ -23,7 +27,8 @@ if [ "$XBPS_TARGET_MACHINE" = i686-musl ]; then
_nopie=yes
fi
-hostmakedepends="pkg-config flex gettext"
+hostmakedepends="pkg-config flex gettext
+ $(vopt_if mingw "cross-${XBPS_TARGET_MACHINE%-musl}-w64-mingw32")"
makedepends="gettext-devel lcms2-devel zlib-devel ncurses-devel
glu-devel libSM-devel libXext-devel libX11-devel libXpm-devel
libXinerama-devel libXcomposite-devel libXmu-devel libXxf86vm-devel
next prev parent reply other threads:[~2021-01-05 4:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 4:38 [PR PATCH] " aeadio
2021-01-05 4:44 ` [PR REVIEW] " ericonr
2021-01-05 4:50 ` ericonr
2021-01-05 4:54 ` aeadio [this message]
2021-01-06 3:42 ` ericonr
2021-01-09 8:06 ` [PR PATCH] [Closed]: " Hoshpak
2021-01-09 18:55 ` aeadio
2021-01-09 19:24 ` Hoshpak
2021-01-09 19:31 ` aeadio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210105045454.m1m8j-kCdk0U1UR3PKHWfh4apHODzPdwxZ0qHcxx5IE@z \
--to=aeadio@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).