February 2025 - Wine-Devel - list.winehq.org

Re: Apple Silicon compilation

by Donald Smith

I’ve also been playing with building wine on Apple Silicon (Sequoia), and though I was also able to successfully build for x86_86 (with Rosetta 2), it seems that I’m having issues with fonts that are basically making running anything with a GUI impossible. I can run cmd.exe without a problem, but things like explorer and notepad either don’t show up at all or open with an essentially blank window. If I configure and build with freetype2, I get repeated errors about not being able to find the library even though I have it installed: Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. http://www.freetype.org Then, eventually the following error: 0140:err:syslink:SYSLINK_SetFont Failed to create link font! Configuring without freetype still results in the above SYSLINK_SetFont error. Attempts after the I’ve found a few vague posts online from long ago about needing the 32-bit freetype2 libraries, but is that even a possibility anymore since Apple removed support for 32-bit code? I’ve also come across hints that System Integrity Protection might be getting in the way somehow, but I’m really not familiar with the details of how that works. In any case, I have just set up a spare Linux box so I can hopefully have a smoother time getting started on contributing, but I was excited about working on this in a macOS environment. After seeing Rob’s post, I figured I would chime in just in case anybody has any tips. Forgive me if I am just way off in the weeds; it has been a long time since I've compiled any C code on Linux, much less on macOS. -Don > > From: robert lippmann <robert.lippmann.development(a)gmail.com> > Subject: Apple Silicon compilation > Date: February 23, 2025 at 7:55:59 PM EST > To: wine-devel(a)winehq.org > Reply-To: wine-devel(a)winehq.org > > > Hi all, > > I tried to update the wiki to document how to compile Wine on Apple Silicon, but I’m not sure if it went through. > > Basically, you need to add lld (which pulls in llvm) in addition to the other build dependencies > So: > > brew install lld > > Then: > PATH=`brew —prefix llvm`/bin:`brew —prefix bison`/bin:$PATH > > Then everything compiles. > > You probably don’t even need Xcode. And you probably should have Rosetta2 installed. > > I haven’t actually been able to get it to run yet, though… > > — Rob >

Feb. 27, 2025

Re: Question about `Avoid const strarray pointers in all functions' patch

by Alexandre Julliard

Mitch Wilkinson <foo.ami(a)yandex.com> writes: > Patch 0828f33e550 (tools: Avoid const strarray pointers in all functions., 2025-02-26)[1] recently landed to `Wine development'. Can anyone > explain me what motivation was behind changing type of function parameter(s)? Does this affect function inlining, or something? There's no performance improvement, it's for consistency with the other similar functions that take an strarray as input. Not passing a pointer makes it obvious that the array is not modified. -- Alexandre Julliard julliard(a)winehq.org

Feb. 27, 2025

Question about `Avoid const strarray pointers in all functions' patch

by Mitch Wilkinson

Feb. 27, 2025

Re: Apple Silicon compilation

by robert lippmann

> On Feb 24, 2025, at 5:55 AM, Dean Greer <gcenx83(a)gmail.com> wrote: > > At minimum Xcode Command Line Tools are required. > If you’re installing llvm, it might not be necessary since you are pulling in a whole new compiler toolchain. But, it’s not like it’s hard to install Xcode and command line tools. > > Also something to keep in mind is a stock upstream wine compile won’t run nicely under Rosetta2. Rosetta2 should work as it is also limited to 4k page sizes. Microsoft Windows arm does something similar using “prism” for running x86 binaries. So, it couldn’t be much worse than running x86 on Windows arm :) In any case, for future reference, if anyone wants to know how to build for arm on apple silicon, the way I outlined would be how to do it.

Feb. 24, 2025

Re: Apple Silicon compilation

by Marc-Aurel Zent

> On 24. Feb 2025, at 11:55, Dean Greer <gcenx83(a)gmail.com> wrote: > > At minimum Xcode Command Line Tools are required. > > And as Stefan has pointed out your pretty much forced to build for x86_64 > > You can compile for x86_64 from an arm Terminal session but it’s simpler to build from an x86_64 Terminal session with ether an Intel brew install or MacPorts. > > Also something to keep in mind is a stock upstream wine compile won’t run nicely under Rosetta2. > I believe stock upstream wine should run decently well under Rosetta 2 in most cases at the moment.

Feb. 24, 2025

Re: Apple Silicon compilation

by Dean Greer

At minimum Xcode Command Line Tools are required. And as Stefan has pointed out your pretty much forced to build for x86_64 You can compile for x86_64 from an arm Terminal session but it’s simpler to build from an x86_64 Terminal session with ether an Intel brew install or MacPorts. Also something to keep in mind is a stock upstream wine compile won’t run nicely under Rosetta2. On Mon, Feb 24, 2025 at 3:39 AM Stefan Dösinger <stefandoesinger(a)gmail.com> wrote: > Am Montag, 24. Februar 2025, 03:55:59 Ostafrikanische Zeit schrieb robert > lippmann: > > Hi all, > > > > I tried to update the wiki to document how to compile Wine on Apple > Silicon, > > but I’m not sure if it went through. > > > Basically, you need to add lld (which pulls in llvm) in addition to the > > other build dependencies > > Generally if you want to run x86 Windows applications run both configure > and > make with arch -x86_64. Then it will all behave as if you were on an Intel > CPU > mac. You don't need to run the built wine with arch because it will be an > x86_64 only binary. > > If you want to build things for arm to run arm64 Windows binaries you are > in a > world of trouble: > > * MacOS won't allow you to map anything below 4 GB, so Wine can't place > the > KSHARED_USER_DATA at 0x7ffe0000. > > * ARM MacOS has 16 kb pages whereas Windows has 4kb ones. > > We are working on both of those issues, but running an arm64 wine is going > to > take a while. > > >

Feb. 24, 2025

Re: Apple Silicon compilation

by Stefan Dösinger

Am Montag, 24. Februar 2025, 03:55:59 Ostafrikanische Zeit schrieb robert lippmann: > Hi all, > > I tried to update the wiki to document how to compile Wine on Apple Silicon, > but I’m not sure if it went through. > Basically, you need to add lld (which pulls in llvm) in addition to the > other build dependencies Generally if you want to run x86 Windows applications run both configure and make with arch -x86_64. Then it will all behave as if you were on an Intel CPU mac. You don't need to run the built wine with arch because it will be an x86_64 only binary. If you want to build things for arm to run arm64 Windows binaries you are in a world of trouble: * MacOS won't allow you to map anything below 4 GB, so Wine can't place the KSHARED_USER_DATA at 0x7ffe0000. * ARM MacOS has 16 kb pages whereas Windows has 4kb ones. We are working on both of those issues, but running an arm64 wine is going to take a while.

Feb. 24, 2025

Apple Silicon compilation

by robert lippmann

Hi all, I tried to update the wiki to document how to compile Wine on Apple Silicon, but I’m not sure if it went through. Basically, you need to add lld (which pulls in llvm) in addition to the other build dependencies So: brew install lld Then: PATH=`brew —prefix llvm`/bin:`brew —prefix bison`/bin:$PATH Then everything compiles. You probably don’t even need Xcode. And you probably should have Rosetta2 installed. I haven’t actually been able to get it to run yet, though… — Rob

Feb. 24, 2025

Wine staging 10.2 release

by Alistair Leslie-Hughes

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 10.2 (350 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * vbscript: implement Join() * shdocvw: Check precisely ParseURLFromOutsideSourceX returned values in tests and make code clearer about that. * oleaut32: Fix logic for deciding whether type description follows the name * oleaut32: Implement decoding of SLTG help strings. * oleaut32: Add support for decoding SLTG function help strings. * oleaut32: Add support for decoding SLTG variable help strings. * oleaut32: OleLoadPicture should create a DIB section for a being loaded bitmap. * oleaut32: Make OleLoadPicture load DIBs using WIC decoder. * gdiplus: Add support for more image color formats. * gdiplus/tests: Add some tests for loading TIFF images in various color formats. Removed (No longer required). * None Added: * [52568] ws_ws2: Support for AF_UNIX sockets. Updated: * vkd3d-latest * win32u-NtGdiExtTextOutW-rotation Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

Feb. 22, 2025

Ask for help

by 谢威

Is there any development documentation related to wine wow64 syscall and unixcall.

Feb. 21, 2025