Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create wine.yml #418

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jonathan-dove
Copy link

A pkg2appimage recipe for wine that can run 32 and 63 bit windows programs on 64bit machines/

A pkg2appimage recipe for wine that can run 32 and 63 bit windows programs on 64bit machines/
@probonopd
Copy link
Member

Thanks @jonathan-dove. Are you sure that this really works? Last time I checked, quite some hacks were needed to get WINE running properly. Please see https://github.com/AppImage/AppImageKit/wiki/Bundling-Windows-applications and https://github.com/sudo-give-me-coffee/wine32-deploy.

@jonathan-dove
Copy link
Author

It does work. I’m currently still testing it on different distros and found a flaw with it that causes it not to work in Centos7 so I’m currently working that out.

@probonopd
Copy link
Member

probonopd commented Apr 23, 2020

Thanks @jonathan-dove.

WINE is a complex beast, much more difficult than most "normal" applications.

Specifically, does it work for 32-bit Windows applications on 64-bit Linux (without 32-bit compat libraries being installed on the system)? This is something the AppImages I have linked above can handle.

@alexdevos
Copy link

Thanks @jonathan-dove for this wine recipe !

I execute the following code (on Debian Stretch) :
wget https://github.com/AppImage/pkg2appimage/releases/download/continuous/pkg2appimage-continuous-x86_64.AppImage
chmod +x pkg2appimage-continuous-x86_64.AppImage
wget https://raw.githubusercontent.com/AppImage/pkg2appimage/573f412d8f7402c0cc55074b6d61da64f67fc7af/recipes/wine.yml
./pkg2appimage-continuous-x86_64.AppImage wine.yml

But I get the following error :
[...]
++ find . -name '*.so' -or -name '*.so.*' -or -type f -executable -exec strings '{}' ';'
++ sed s/GLIBC_//g
++ sort --version-sort
++ uniq
++ tail -n 1
+ GLIBC_NEEDED=2.3
+ VERSION_EXPANDED=.glibc2.3
+ set +x
appimagetool, continuous build (commit 7392c48), build 2120 built on 2020-03-10 18:42:43 UTC
Error: no such file or directory: ./Wine.AppDir/

Do you have an idea what's going on ?

@thenoobtester
Copy link

thenoobtester commented Jun 25, 2021

Hi,

I have tried on Debian stretch too and it's not working, when I run it I get :

`/tmp/.mount_1Wine-JguNcg/AppRun: line 9: wine: command not found

/tmp/.mount_1Wine-JguNcg/AppRun: line 10: exec: wine: not found
`
Would it be possible to upload a working appimage, i have been looking for something like this for ages.

Thank you

@ruanformigoni
Copy link

ruanformigoni commented Oct 27, 2022

@probonopd I think that wine now works without hacks required for glibc, I've made a fork from mmtrt, updated the sources to jammy from focal in the appimagebuilder recipe, and the /usr/bin/wine: No such file or directory is fixed in fresh linux mint installs, without libc6-i386. Here are some tests I've made, it worked in bionic, jammy and focal. Here is a proof of concept release: https://github.com/ruanformigoni/wine/releases/tag/continuous-staging. I think it may be wow64 in action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants