How to install wine mono
How to install wine mono
How to install wine mono
Post by johnywhy » Sun May 03, 2015 4:58 am
first time you start wine, it asks you to download mono. If you skip or cancel it, it never asks again.
how can you force wine to download mono, if you skipped or cancelled the first time?
Re: How To Manually Install Mono?
Post by dimesio » Sun May 03, 2015 5:48 am
Re: How To Manually Install Mono?
Post by johnywhy » Sun May 03, 2015 5:51 am
that’s not a can’t, it’s a can.
does this download also include gecko? because same thing happens with gecko.
Re: How To Manually Install Mono?
Post by dimesio » Sun May 03, 2015 6:51 pm
Have you checked your distro for wine-mono and wine-gecko packages? Most distros package them. You will still have to manually run the msi files to install wine-mono and wine-gecko to existing wineprefixes, but they will automatically be installed to any new wineprefixes.
Re: How To Manually Install Mono?
Post by johnywhy » Mon May 04, 2015 5:51 pm
i’m using a minimized slackware distro (puppy slacko). wine is available as a minimized package which does not bundle mono and gecko.
attempting to install mono, i get:
getting same on the gecko package you linked, and also on dotnetfx.exe
currently using wine 1.7.41.
thx for any suggestions.
Re: How To Manually Install Mono?
Post by dimesio » Mon May 04, 2015 9:42 pm
Re: How To Manually Install Mono?
Post by johnywhy » Mon May 04, 2015 11:30 pm
Seems like Wine and Gecko didn’t install.
Is there a test?
Re: How To Manually Install Mono?
Post by dimesio » Tue May 05, 2015 7:42 am
How to install wine mono
Contents
Installing
From source
From a source tree, you can use the «make dev» target to build Wine Mono and configure the current Wine prefix (default or as set by the WINEPREFIX environment variable) to use the build. The «make dev-setup» target will just configure the Wine prefix without building.
Shared Install
For packagers, and users with multiple prefixes, a shared install is recommended.
To create a shared install, download the appropriate binary tarball from https://dl.winehq.org/wine/wine-mono/ (or build it from source with «make bin») and extract it to the appropriate location.
Wine will search for Wine Mono in the following places (replacing 5.0.0 with the expected version):
Prefix Local Install
Wine will automatically download and install the appropriate Wine Mono MSI on prefix update, so this shouldn’t usually be necessary.
If you wish to use a different MSI installer than the one you’d get automatically:
The installer normally gives no feedback when it succeeds. You can run «wine uninstaller» again to check that you have the version you expect.
Versions
| Wine Version | Wine Mono Version |
|---|---|
| 7.10 | 7.3.0 |
| 7.6 | 7.2.0 |
| 7.2 | 7.1.1 |
| 6.22 | 7.0.0 |
| 6.18 | 6.4.0 |
| 6.14 | 6.3.0 |
| 6.10 | 6.2.0 |
| 6.6 | 6.1.1 |
| 6.2 | 6.0.0 |
| 5.19 | 5.1.1 |
| 5.11 | 5.1.0 |
| 5.7 | 5.0.0 |
| 4.20 | 4.9.4 |
| 4.17 | 4.9.3 |
| 4.14 | 4.9.2 |
| 4.11 | 4.9.0 |
| 4.7 | 4.8.3 |
| 4.6 | 4.8.1 |
| 4.3 | 4.8.0 |
| 4.0-rc6 | 4.7.5 |
| 3.13 | 4.7.3 |
| 2.14 | 4.7.1 |
| 2.4 | 4.7.0 |
| 2.0-rc1 | 4.6.4 |
| 1.9.12 | 4.6.3 |
| 1.9.8 | 4.6.2 |
| 1.9.5 | 4.6.0 |
| 1.7.37 | 4.5.6 |
| 1.7.32 | 4.5.4 |
| 1.7.7 | 4.5.2 |
| 1.5.16 | 0.0.8 |
| 1.5.5 | 0.0.4 |
Building
Debugging
As of Wine Mono 0.0.4, the WINE_MONO_TRACE environment variable may be set as follows to trace calls within Mono:
This option is the same as the --trace option in Mono.
Activating any trace at all, even a bogus assembly name, will cause Mono to print out all exceptions as they occur. This can be useful, but it can also be misleading as some exceptions are perfectly normal.
Sometimes Mono’s inlining can obscure the source of an exception, especially NotImplementedException. This can be worked around by setting MONO_INLINELIMIT=0.
Setting WINE_MONO_VERBOSE=1 will display the addresses of all JIT-compiled methods. Setting MONO_VERBOSE_METHOD=MethodName will display detailed information about the method’s compilation, and break into the debugger if one is attached.
Documentation
Test Suite
The tests can be built using «make tests» in the build tree or downloaded from https://github.com/madewokherd/wine-mono/releases. The «make tests-zip» target will build a zip file for running outside the build tree.
To run the full test suite in Wine, use the «make test» target.
To run the full test suite in Windows, use run-tests.exe with no arguments.
Specific test names can be passed to run-tests.exe as arguments, for example:
Note that this particular Mono environment is only intended for building Wine Mono components, and may not accurately reflect the state of upstream Mono. Also, many of the tests only work in a Win32 environment.
Test source code can be found in tools/tests, mono/mono/tests, mono/mcs/class/*/Test, and mono-basic/vbruntime/Test. See https://www.mono-project.com/community/contributing/test-suite/ for information on Mono’s tests.
C# interpreter
A C# interactive interpreter is also included with the tests, in the csharp directory.
How to install wine mono
Updated: May 20, 2019
Linux. WINE. Interesting use case. As it happens, I was playing with WINE, trying to install some Windows software. Turns out, the particular program is available natively, so no biggie, but occasionally, I am trying this framework, to see if it’s made progress in becoming simpler and easier.
On this particular rainy day, I was not having success with Mono, or dotNET if you will. The application couldn’t run, because there was Mono missing on my Linux box, but getting it configured correctly was far from trivial. Hence this tutorial. Someone somewhere out there may have an obscure use case, and this little guide shall come handy one day. Or not. After me.
Error that be
003a:err:mscoree:CLRRuntimeInfo_GetRuntimeHost Wine Mono is not installed
Self evident, no? Well, the solution is to install the complete Mono framework, which is done by specifying the mono-complete meta package. I tested this on an Ubuntu-based system, so don’t hate me if the naming convention is different in your distro:
sudo apt-get install mono-complete
Alas, this did not help.
Solution 1: Official Mono installer
You can grab the package from the official WINE website, and then install it using the Add/Remove functionality via wine uninstaller as I’ve shown you a few weeks back. Select Add, select the Mono MSI package, and that should be all.
In my case, I did make progress, but not enough. A new error message:
002f:err:mscoree:LoadLibraryShim error reading registry key for installroot
Solution 2: Winetricks
I decided to go old school and fall back to this neat little wrapper script, which you can use to install tons of common Windows applications, libraries and utilities, and hopefully, not have to deal with any fancy errors. I installed the script from the repos, and then installed dotNET 4.5 using it.
sudo apt-get install winetricks
The UI launched, and I started clicking buttons. Progress was made. Errors came up, but the wizard did not crash. The errors are far from helpful, and unless they block the installation, they should not be shown.
If you’re wondering, my test program was KeePass, which is also available through the repos. But as it happens, the Windows versions comes with a nicer icon and better system area integration, at least in Plasma, but the UI itself is more visually pleasing natively, possibly due to font DPI and whatnot. So overall, I was rather happy, as usually, I had little luck with WINE attempts in the past.
Conclusion
Here we go. Success! Now, this does not mean we’re now in the golden age of Windows-Linux compatibility. Not at all. But every little bit of progress we make is good and useful, especially if it helps people gain more freedom in their software choice. Native solutions are always the best option, but if there ain’t one, you can dabble in WINE.
The big issue with this framework is that there’s no golden formula. You can’t just say, do these four steps and all your applications will install and run well. Nope. There’s a fair amount of chance and luck, and some of the setups can be quite convoluted. I guess this one ranges midway on that scale. But we’ve accomplished our task. You wanted Mono, you got Mono. Happy Linuxing. I mean Winduxing.
Ubuntu
Translations of this page: 
简体中文 
Nederlands
Installing WineHQ packages
The WineHQ repository key was changed on 2018-12-19. If you downloaded and added the key before that time, you will need to download and add the new key and run sudo apt update to accept the repository changes.
Ubuntu 18.04/Linux Mint 19.x do not provide FAudio, which is a dependency of Wine versions prior to 6.21. Users of the current wine-stable packages will need to install this. Follow the instructions in https://forum.winehq.org/viewtopic.php?f=8&t=32192 to install FAudio from the OBS. (FAudio packages for Ubuntu 19.10 and later are in the distro’s universe repository.)
Apt-key is now deprecated. If you get a warning about this, remove the key with:
sudo apt-key del «D43F 6401 4536 9C51 D786 DDEA 76F1 A20F F987 672F»
And remove the the line about the WineHQ repository from /etc/apt/sources.list.
If you have previously installed a Wine package from another repository, please remove it and any packages that depend on it (e.g., wine-mono, wine-gecko, winetricks) before attempting to install the WineHQ packages, as they may cause dependency conflicts.
If your system is 64 bit, enable 32 bit architecture (if you haven’t already):
Download and add the repository key:
Add the repository:
Enable 32-bit Architecture