From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: winegui-2.3.5
Date: Sun, 11 Feb 2024 19:19:16 +0100 [thread overview]
Message-ID: <20240211181916.765CF27B7C@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48642@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]
There's a closed pull request on the void-packages repository
New package: winegui-2.3.5
https://github.com/void-linux/void-packages/pull/48642
Description:
Introducing WineGUI package. At last, a user-friendly Wine graphical interface.
I'm the developer of [WineGUI](https://gitlab.melroy.org/melroy/winegui).
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
The x86_64 build went fine. I also tested the WineGUI application itself, running on Void Linux. I did notice that wine-32bit was missing as well. But multilib can't be added as depends too bad!
Hence I added a `README.voidlinux`, just like the Steam package. However, I hope there will be a **better solution** in the neat future.
I also tried `armv6l` and `armv7l` cross-builds, but this seems to fail on wine? That is too bad.
```sh
=> wine-9.1_1: the following build options are set:
mingw: Use the MinGW cross compiler to build WinPE DLLs (ON)
xshm: Enable support for the X Shared Memory Extension (ON)
staging: Apply the wine-staging patchset (OFF)
=> ERROR: wine-9.1_1: this package cannot be built for armv6l.
```
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc) -> OK
- I tried to build this PR locally for these architectures, but failed...:
- armv7l
- armv6l
next prev parent reply other threads:[~2024-02-11 18:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 21:05 [PR PATCH] " melroy89
2024-02-10 22:42 ` [PR PATCH] [Updated] " melroy89
2024-02-10 22:49 ` melroy89
2024-02-11 0:09 ` [PR PATCH] [Updated] " melroy89
2024-02-11 0:11 ` melroy89
2024-02-11 0:13 ` melroy89
2024-02-11 2:06 ` chrysos349
2024-02-11 3:18 ` [PR PATCH] [Updated] " melroy89
2024-02-11 3:21 ` melroy89
2024-02-11 3:23 ` melroy89
2024-02-11 3:32 ` melroy89
2024-02-11 14:18 ` [PR REVIEW] " ahesford
2024-02-11 15:07 ` melroy89
2024-02-11 15:14 ` melroy89
2024-02-11 15:46 ` melroy89
2024-02-11 16:47 ` ahesford
2024-02-11 16:48 ` ahesford
2024-02-11 18:19 ` ahesford [this message]
2024-02-11 18:19 ` ahesford
2024-02-11 19:30 ` melroy89
2024-02-11 20:18 ` [PR REVIEW] " melroy89
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=20240211181916.765CF27B7C@inbox.vuxu.org \
--to=ahesford@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).