08-15-2022, 05:25 PM
You have to call "wine" on Linux so it executes Windows programs:
Of course, change "Wavosaur" and the paths to what you want to test. Remember the letter case of everything has to match!
This could depend on the version of Wine. I have v7.12 on Fedora 36 XFCE which is almost the latest version. If you use Debian or anything based directly on it, they're still on v5; it might work but I should have tested that. Ubuntu is based on Debian but does things a bit differently and therefore could get Wine v6 with that and the other 'untus. I haven't tested that neither, I really should.
Wine on Debian should be able to handle nearly any QB64-created program while Galleon was the top man of the project (ie. 32-bit only).
Upon installing Wine it might ask to download "mono" module. This sucks because Wine is a big download already without it, and with "mono" included it could take as much as 1GB of hard disk space. If this is not done then some programs written c. 2012 and later might not work, otherwise those programs specifically compiled with M$ Visual Studio-dot-NET. You could forego "gecko" but as a result will not be able to open help files in CHM format.
One more thing to watch out for is that if your EXE file is 32-bit, you might have to make sure "multilib" mode is enabled on your Linux system. Some Linux distros like Void offer Wine in 64-bit only unless a package is downloaded so that 32-bit libraries as well as 64-bit are included in complex dependencies. A Wine install which is 64-bit only will refuse to run a 32-bit Windows program. Also when running "winecfg" it nags the user LOL telling him/her to install 32-bit edition even if it's not possible.
Even worse is conflicting releases of the same version, as I've experienced on EndeavourOS (based on Arch); I wanted both 32-bit and 64-bit Wine. While 32-bit was the absolute latest, 64-bit had various earlier releases and, after acquiring the former, when I tried to get the latter as well the package manager warned the two versions conflicted. The other thing was the 32-bit library was in the "standard" repository of that particular distro, while 64-bit was from the Arch Users Repository (AUR).
Maybe the forum doesn't let you tag me B+ because you already did so. LOL.
Code: (Select All)
dim a$
a$ = environ$("HOME")
a$ = "wine " + a$ + "/zapp/Wavosaur/Wavosaur.exe"
shell _hide a$
print "Did it work or not?!"
endOf course, change "Wavosaur" and the paths to what you want to test. Remember the letter case of everything has to match!
This could depend on the version of Wine. I have v7.12 on Fedora 36 XFCE which is almost the latest version. If you use Debian or anything based directly on it, they're still on v5; it might work but I should have tested that. Ubuntu is based on Debian but does things a bit differently and therefore could get Wine v6 with that and the other 'untus. I haven't tested that neither, I really should.
Wine on Debian should be able to handle nearly any QB64-created program while Galleon was the top man of the project (ie. 32-bit only).
Upon installing Wine it might ask to download "mono" module. This sucks because Wine is a big download already without it, and with "mono" included it could take as much as 1GB of hard disk space. If this is not done then some programs written c. 2012 and later might not work, otherwise those programs specifically compiled with M$ Visual Studio-dot-NET. You could forego "gecko" but as a result will not be able to open help files in CHM format.
One more thing to watch out for is that if your EXE file is 32-bit, you might have to make sure "multilib" mode is enabled on your Linux system. Some Linux distros like Void offer Wine in 64-bit only unless a package is downloaded so that 32-bit libraries as well as 64-bit are included in complex dependencies. A Wine install which is 64-bit only will refuse to run a 32-bit Windows program. Also when running "winecfg" it nags the user LOL telling him/her to install 32-bit edition even if it's not possible.
Even worse is conflicting releases of the same version, as I've experienced on EndeavourOS (based on Arch); I wanted both 32-bit and 64-bit Wine. While 32-bit was the absolute latest, 64-bit had various earlier releases and, after acquiring the former, when I tried to get the latter as well the package manager warned the two versions conflicted. The other thing was the 32-bit library was in the "standard" repository of that particular distro, while 64-bit was from the Arch Users Repository (AUR).
Maybe the forum doesn't let you tag me B+ because you already did so. LOL.