Github messages for voidlinux
 help / color / mirror / Atom feed
From: fvalasiad <fvalasiad@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: wine: update to 9.0
Date: Wed, 17 Jan 2024 18:42:44 +0100	[thread overview]
Message-ID: <20240117174244.5AE1B294D3@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48249@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

New comment by fvalasiad on void-packages repository

https://github.com/void-linux/void-packages/pull/48249#issuecomment-1896293268

Comment:
> The new WoW64 mode looks interesting however it seems like activating it would compromise too much on compatibility and performance so I would prefer to keep building the old way for now and activate the new mode only after it has been improved in a future version or if we wanted to drop i686 and multilib support.
> 
> Building for aarch64 would certainly be useful for some people however I don't own any aarch64 hardware right now so I couldn't test the resulting build myself.

I have a couple of SBCs and PIs around, want me to run a quick void install on em and try out wine with some basic x86 windows programs?

I am not that familiar with configuring the template for other architectures though, I will need some time to figure out how to make a package. Otherwise I cross compile wine normally and simply move the bundle to my pi and test run it there, then we invest in the arm package.

  parent reply	other threads:[~2024-01-17 17:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 15:10 [PR PATCH] " fvalasiad
2024-01-17 15:14 ` [PR PATCH] [Updated] " fvalasiad
2024-01-17 15:17 ` fvalasiad
2024-01-17 17:20 ` [PR REVIEW] " Hoshpak
2024-01-17 17:20 ` Hoshpak
2024-01-17 17:29 ` [PR PATCH] [Updated] " fvalasiad
2024-01-17 17:30 ` [PR REVIEW] " fvalasiad
2024-01-17 17:31 ` fvalasiad
2024-01-17 17:34 ` Hoshpak
2024-01-17 17:42 ` fvalasiad [this message]
2024-01-18 13:12 ` AlexKurisu
2024-01-18 14:38 ` fvalasiad
2024-01-18 14:40 ` fvalasiad
2024-01-18 14:58 ` AlexKurisu
2024-01-18 17:03 ` Hoshpak
2024-01-18 17:03 ` Hoshpak
2024-01-18 17:03 ` Hoshpak
2024-01-18 17:33 ` [PR PATCH] [Updated] " fvalasiad
2024-01-18 17:36 ` fvalasiad
2024-01-18 18:04 ` fvalasiad
2024-01-19 23:14 ` [PR PATCH] [Updated] " fvalasiad
2024-01-19 23:41 ` fvalasiad
2024-01-20  8:57 ` [PR PATCH] [Merged]: " Hoshpak

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=20240117174244.5AE1B294D3@inbox.vuxu.org \
    --to=fvalasiad@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).