Hello,
I don't know if it's the new way to create qb64 (using a make file) but there is kind of a problem on Linux.
Yes, both the qb64 executable itself and the executable it creates can't be started anymore with a double click on their relevant file icon.
You still can launch qb64 with the command "./qb64" (when you're in its folder), but there was not this problem with the 2.0.2 nor with any other previous releases.
Question: just to make a test, is it still possible to compile QB64 Phoenix Edition with the method of the previous 2.0.2 setup_lnx.sh bash script?
If yes, what are the modifications (if any) to make to that previous bash script to successfully compile qb64 0.8.2 ?
Another "glitch": if you place qb64 into a folder with a name containing a space (e.g. "/home/me/qb64 official"), then the run_qb64.sh bash script generated by the setup_lnx.sh bash script will not work.
TIA
Cheers.
Fifi
I don't know if it's the new way to create qb64 (using a make file) but there is kind of a problem on Linux.
Yes, both the qb64 executable itself and the executable it creates can't be started anymore with a double click on their relevant file icon.
You still can launch qb64 with the command "./qb64" (when you're in its folder), but there was not this problem with the 2.0.2 nor with any other previous releases.
Question: just to make a test, is it still possible to compile QB64 Phoenix Edition with the method of the previous 2.0.2 setup_lnx.sh bash script?
If yes, what are the modifications (if any) to make to that previous bash script to successfully compile qb64 0.8.2 ?
Another "glitch": if you place qb64 into a folder with a name containing a space (e.g. "/home/me/qb64 official"), then the run_qb64.sh bash script generated by the setup_lnx.sh bash script will not work.
TIA
Cheers.
Fifi
Before to send the arrow of truth, dip the head in a honey pot (Cheyenne saying).
Don't tell my Mom I'm on iMac with macOS, she thinks I work on PC with Windows. 