07-01-2022, 04:39 PM
(06-29-2022, 03:16 AM)Fifi Wrote: 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.
That's quite odd, I'm not really sure what to make of that. Do you know what the last version this worked in was? In particular did it start appearing in v0.7.0? The only thing I can think of is if the file isn't marked executable, but you shouldn't be able to run it via the command line either if that's the case.
I guess to clarify - by "file icon" do you mean the menu entry, or the icon when viewed in the file browser?
(06-29-2022, 03:16 AM)Fifi Wrote: 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?
No, all the previous build logic is gone. In v0.8.2 you might be able to get it to work if you put the various old build files back in place, but probably not.
(06-29-2022, 03:16 AM)Fifi Wrote: 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.
Good catch, yeah that's a bug, it looks like it's missing some quotes. Quite strange that you're only finding it now, that's probably a decade old bug