+- QB64 Phoenix Edition (https://qb64phoenix.com/forum)
+-- Forum: Chatting and Socializing (https://qb64phoenix.com/forum/forumdisplay.php?fid=11)
+--- Forum: General Discussion (https://qb64phoenix.com/forum/forumdisplay.php?fid=2)
+--- Thread: Making QB64 work on Linux (/showthread.php?tid=673)
Pages:
1
2
RE: Making QB64 work on Linux - SpriggsySpriggs - 09-15-2022
I'm glad I don't often use Linux. It seems like it ends up being a complicated and painful mess. I use it only for very rare occasions.
RE: Making QB64 work on Linux - mnrvovrfc - 09-24-2022
Void Linux (64-bit "libc" *not* "musl"): It looks like the "setup_lnx.sh" would need better logic for existence of "make" utility. This didn't happen before, why is it happening? I'm showing a bit of what happened to me at the terminal a short time ago.
Code: (Select All)
[xx@xxxxxxxx qbpe]$ ./setup_lnx.sh
VoidLinux detected.
Compiling and installing QB64-PE...
./setup_lnx.sh: line 112: make: command not found
./setup_lnx.sh: line 113: make: command not found
It appears that the qb64pe executable file was not created, this is usually an indication of a compile failure (You probably saw lots of error messages pop up on the screen)
Usually these are due to missing packages needed for compilation. If you're not running a distro supported by this compiler, please note you will need to install the packages listed above.
If you need help, please feel free to post on the QB64 Phoenix Edition Forums detailing what happened and what distro you are using.
Also, please tell them the exact contents of this next line:
DISTRO: voidlinux
Thank you for using the QB64-PE installer.
[xx@xxxxxxxx qbpe]$ sudo xbps-install make
Password:
Name Action Version New version Download size
make install - 4.3_3 489KB
Size to download: 489KB
Size required on disk: 1997KB
Space available on disk: 16GB
Do you want to continue? [Y/n] y
[*] Downloading packages
make-4.3_3.x86_64.xbps.sig: 512B [avg rate: 7813KB/s]
make-4.3_3.x86_64.xbps: 489KB [avg rate: 602KB/s]
make-4.3_3: verifying RSA signature...
[*] Collecting package files
make-4.3_3: collecting files...
[*] Unpacking packages
make-4.3_3: unpacking ...
[*] Configuring unpacked packages
make-4.3_3: configuring ...
make-4.3_3: installed successfully.
1 downloaded, 1 installed, 0 updated, 1 configured, 0 removed.
[xx@xxxxxxxx qbpe]$ ./setup_lnx.sh
VoidLinux detected.
Compiling and installing QB64-PE...RE: Making QB64 work on Linux - mnrvovrfc - 10-01-2022
Knoppix. This one is unique, so unique it comes with Wine v5 which might help fill in all the dependencies to build QB64PE.
The problem is that 32-bit QB64PE is built!
It means that if you create an executable file with the QB64PE compiler from that system, which will be 32-bit, then copy it to a 64-bit-only system that user's program file would refuse to run unless there is a "multilib" arrangement. So beware and use at your own risk.
Not saying the distro is bad. Knoppix is a 64-bit operating system. It's weird in places and it's not meant to be cutting-edge. It could be taken seriously, unlike what some people think, but it hasn't been updated in 1-1/2 years. It has something which works like persistence, like a "savefile" but it's transparent to the user. (Porteus, Puppy and a few others might be better allowing a "fresh start" or "load into RAM.") Processing could be slow because it compressed all programs it comes with to save disk space. The "knoppix" account has "sudo" privileges but one doesn't have to provide the password, because it's not possible to know what is the password. It comes with a lot of games LOL. Because the OS package was supposed to fill in a whole single-sided DVD, it comes with three desktop environments, LXDE (which it fires up at first), GNOME and KDE. A source of confusion is multitude programs like file managers and compressed-archive managers, but just choose one that is suitable. That said, LXDE file manager feels buggy like Thunar. Hate GNOME and have some problems on my computer trying to display Plasma, which forced me to ditch Ubuntu Studio a few months ago.
The "qb64pe" executable, on Knoppix when it's processed by "readelf" program lists the same libraries which are "NEEDED"; however those libraries are 32-bit on this OS. I don't know how to convince "apt" to enable "multilib" or install 64-bit versions of those libraries so it could create "qb64pe" 64-bit binary and the QB64PE compiler also creates 64-bit executable files.
Don't be scared off by what is said here and in other places. Grab the DVD image and burn it onto a 16GB or 32GB external USB disk and go about your business with it. Note that you won't be able to use the rest of the disk for eg. FAT32 partition that WIndows could recognize.
RE: Making QB64 work on Linux - mnrvovrfc - 10-05-2022
Just unpack somewhere in your user area and run "setup_lnx.sh", no need even to turn on the modem while using "Liveslack DAW". This is a live version of Slackware "-current" which focuses a lot on music software, a lot like Ubuntu Studio but without the likes of Blender and Libreoffice. Like that other distro it comes only with KDE Plasma desktop environment so a lot of KDE apps like Elisa (music player, worthless since it has VLC Media Player as dependency), Falkon (web browser), Kate/KWrite (text editor), KDEnlive (video editor), KWave (audio editor) and Okular (PDF viewer). It comes with almost no games, though, two variations of chess it seems. (I suck at chess, cannot even beat "beginning" computer.) It includes Firefox and GIMP. It also has XMMS which is a few decades old LOL but could play music tracker modules.
Getting a well-behaved setup with this version of Slackware live, with persistence is a PITA, must have the ISO as well as two disks especially if you're like I am insisting on external USB gear. Must "burn" the ISO to one USB drive, in order to run a script to "install" to the other disk. It could probably be installed to HDD/SDD, however it's not recommended since it's "-current" (unstable) and not the Slackware v15 "install DVD" that came out seven months ago.
I said the downloaded ISO is a PITA because it failed to boot via EFI for me, but the live "install" boots successfully. It's not possible to enable persistence during a session with the downloaded ISO unless there's a way I don't know of to unpack the ISO, add a directory, somehow make the whole thing writable and then bundle it into an ISO again. I know it's possible with File Roller/Engrampa available for Ubuntu, also a couple of free programs and payware for Windows. Also the "persistence" becomes the rest of the disk that it doesn't use which won't be readable by Windows but could add other Linux applications that are like QB64PE instead of "packaged".
Long live the Slack!
RE: Making QB64 work on Linux - mnrvovrfc - 10-12-2022
(10-05-2022, 07:04 AM)mnrvovrfc Wrote: Long live the Slack!Warning: if you must have Wine, because you would still like to run 32-bit Windows apps then it might be best to avoid Slackware. Avoid Salix (Slackware clone) too because it's 64-bit only pretty much and it seems no "multilib" could be installed from "Gslapt" package manager. "wine-staging" is not the same as Wine for Salix.
It's possible to pick Slackware 32-bit but keep in mind that executable programs created by QB64PE built there (and any other programming system) will be 32-bit and will not run on a 64-bit-only system (ie. without "multilib").
Otherwise no problem installing and building QB64PE on those two distros.
RE: Making QB64 work on Linux - vividpixel - 10-13-2022
I'll chime in to say no issues running the setup script and getting going on Ubuntu, though I can't say I'd recommend Ubuntu itself--seems like in 15 years it's gotten worse. One recent hiccup being I entirely lost the system settings and anything you can access from there. Now I'm not sure what other distro to try if it's difficult or crippled on non-Debian ones!
RE: Making QB64 work on Linux - cage - 10-13-2022
I have had no problems with the script on Arch Linux. QB64phx works with no problems other then trying to run programs designed to run on Windows. All the utilities I have written for Linux work as expected. My only exception would be to have a Windows and Linux sections on this website. Other than that I have use QB64 for many years, both on Windows and now Linux.
RE: Making QB64 work on Linux - Kernelpanic - 10-13-2022
(10-13-2022, 02:47 AM)vividpixel Wrote: I'll chime in to say no issues running the setup script and getting going on Ubuntu, though I can't say I'd recommend Ubuntu itself--seems like in 15 years it's gotten worse. One recent hiccup being I entirely lost the system settings and anything you can access from there. Now I'm not sure what other distro to try if it's difficult or crippled on non-Debian ones!
Try it with openSuse. Under Win 11 you can also use the Windows Subsystem for Linux (WSL 2) with a graphical GUI, including QB64, without having to install a separate Linux system. - Install support for Linux GUI apps
RE: Making QB64 work on Linux - mnrvovrfc - 10-25-2022
Quote:/opt Directory for storing second-tier software packages installed by system users.From:
https://peropesis.org/user-manual/#layout-of-the-Peropesis-file-system
I feel I have to discuss this. In the past QB64 was very much married to its "home" directory; all programs created by the compiler were placed in the same level as "qb64.exe" on Windows. There has been an attempt to take the programming system away from that. This is where this "/opt" thing could make sense. Otherwise it is not recommended on Linux to install QB64PE to that directory unless you know what you're doing. Install instead to a directory somewhere inside your regular user's account, like "$HOME/(username)/qb64pe". Running stuff only as "root" is dangerous, it's like how users were permitted pretty much in WindowsXP and earlier and therefore M$ felt they had to restrain them starting with UAC. Linux offers absolutely no protection from "accidental" installation nor removal of programs for "root" user. To install to "/opt", must have "root" permission which is the reason why I'm saying that. I don't like having to type in my password over and over to get one thing done, I don't know about you guys.
Maybe I could have erased most of what is said above, because the "qb64pe/internal/temp" and other directories would have to be moved. If QB64PE were installed to "/opt" they will also need "root" permission at least temporarily, for the regular user trying to use the product.
No LOL I'm not suggesting Peropesis OS, this is very small and basic (no GUI, no window manager and no graphical web browser) and would need to be bloated impressively so it supports QB64PE.