How do I build this custom Wine wrapper?

Questions about Wine on macOS.
Post Reply
Moonwave
Level 2
Level 2
Posts: 12
Joined: Mon Jan 20, 2020 3:12 pm

How do I build this custom Wine wrapper?

Post by Moonwave » Thu Sep 17, 2020 2:02 am

I want to build a custom Wine wrapper from this link: https://gitlab.com/farmboy0/wine

Can someone let me know some way I can achieve this? I am familiar with Wine but so far I have only used official versions inside Wineskin Winery.

Thanks for any help.

Gcenx
Level 6
Level 6
Posts: 515
Joined: Mon Dec 25, 2017 12:11 pm

Re: How do I build this custom Wine wrapper?

Post by Gcenx » Thu Sep 17, 2020 9:30 am

That looks like gallium nine, if that’s the case it won’t work on macOS.

Also your question doesn’t make much sense, I’ll assume you were asking the following;

- How do I build (wine-nine) from source on macOS
- How to turn the compile into an Engine for Wineskin Winery

Moonwave
Level 2
Level 2
Posts: 12
Joined: Mon Jan 20, 2020 3:12 pm

Re: How do I build this custom Wine wrapper?

Post by Moonwave » Thu Sep 17, 2020 12:05 pm

Gcenx wrote:
Thu Sep 17, 2020 9:30 am
That looks like gallium nine, if that’s the case it won’t work on macOS.
- How do I build (wine-nine) from source on macOS
- How to turn the compile into an Engine for Wineskin Winery
Hi Gcenx,

Thanks for the reply. I actually don't need gallium nine.

Specifically all I need is this one patch: https://gitlab.com/farmboy0/wine/commit ... ea572ce99a

I am looking to learn how to create a Wine wrapper with a patch on Mac OS.

Gcenx
Level 6
Level 6
Posts: 515
Joined: Mon Dec 25, 2017 12:11 pm

Re: How do I build this custom Wine wrapper?

Post by Gcenx » Thu Sep 17, 2020 2:11 pm

You need to setup a development environment to compile wine from source see macOS/Building, that will provide the basic requirements.

Here’s the commit as a patch, this patch only applies to the X11 display driver not macDriver.

Download wines source at what ever version you intend on using, apply the patch then run configure/make as needed.

Turning the compile into a Wineskin engine is simple the layout is as follows;

wswine.bundle
bin
lib
share
version (contains the Engines name)

Compress as .tar, ensure archives name matches the engine name, then compress using 7z.

The resulting Engine should look something like
WS9Wine4.0.tar.7z, place this into ~/Library/Application Support/Wineskin/Engines

Post Reply