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

Debian Wine Setup: command not found: wine64 #8308

Open
2 tasks done
SteffenBlake opened this issue May 19, 2024 · 3 comments
Open
2 tasks done

Debian Wine Setup: command not found: wine64 #8308

SteffenBlake opened this issue May 19, 2024 · 3 comments

Comments

@SteffenBlake
Copy link

Prerequisites

  • I have verified this issue is present in the develop branch
  • I have searched open and closed issues to ensure it has not already been reported.

MonoGame Version

N/A

Which MonoGame platform are you using?

N/A

Operating System

Debian 6.1.90-1

Description

Following the steps here:
https://docs.monogame.net/articles/getting_started/1_setting_up_your_development_environment_unix.html#optional-setup-wine-for-effect-compilation

After installing the packages, /usr/lib/wine/wine64 was created, yet it wasnt properly added to PATH properly.

Which in turn caused the script after to fail, as it could not resolve the executable wine64

command not found: wine64

adding the following to my ~/.*rc file for my shell resolved this issue, so we may want to add a note about this potential issue on the documentation (If someone links me to where that is maintained I can submit the tweak myself if needed)

export PATH=$PATH:/usr/lib/wine

Steps to Reproduce

Follow the steps here:
https://docs.monogame.net/articles/getting_started/1_setting_up_your_development_environment_unix.html#optional-setup-wine-for-effect-compilation

On latest Debian distro

Minimal Example Repo

No response

Expected Behavior

Secondary script runs without error

Resulting Behavior

Wine64 is not on PATH, so the script cannot find it

Files

No response

@stromkos
Copy link
Contributor

Please note that the docs are somewhat out of date and differences in Linux distributions are not easy to keep up with.

For modern versions of wine the PE type determines the 32-64 bit divide, so replacing wine64 with wine in the downloaded shell script should resolve the issue without polluting the PATH.

OR:

Create a link to the wine64 manually: (Requires root permissions)

ln -s /usr/lib/wine/wine64 /usr/bin/wine64

Your solution is best when root permissions are not available (after install):

export PATH=$PATH:/usr/lib/wine

Or when installed into ~/usr/lib/wine


There is no simple common solution for all possibilities.

@SteffenBlake
Copy link
Author

SteffenBlake commented May 21, 2024

I actually tried that first solution initially as a workaround, both actually proceed to fail with wine failing to find dotnet, it doesn't show up under system32 and you get some file not found errors from Wine.

The only solution that actually worked was truly using the proper wine64 executable for me, which was installed but just not added to PATH for some reason.

But for sure alternatively symlinking it to bin should be just as good of a solution as well!

@stromkos
Copy link
Contributor

both actually proceed to fail with wine failing to find dotnet.

Interesting, my last experience required DotNet framework installed in the wine environment.

The instructions were written for Ubuntu not Debian, and made some assumptions.

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

No branches or pull requests

2 participants