06-05-2023, 06:08 AM
Welcome to the forums.
You have to understand QB64 has to translate BASIC code to C++ to then relay it to "g++" and other tools that comprise the GNU Compiler Collection ("gcc"). That takes time. If you take a short look at "(qb64pe)/internal/temp" directory, you will notice a few hundred text files which is the result of the translations. "(qb64pe)" is the directory where you installed QB64PE.
Each version of QB64 has compiled to executable slower than the previous, but because of the way the programming system has expanded. The Phoenix Edition v3 is more complex than Galleon's efforts before QB64 hit version 1. There are many more programs involved in the creation of executables, and perhaps some Python and some other interpreter. Before v0.98 on Windows, a bunch of DLL files were required pre-installed so the user executable could run. Now everything that is needed by the executable is packed into it which increases compilation and linking time. But computers these days have plenty of RAM, and if nothing else really heavy is being done by another program or by one written with QB64 then the wait shouldn't be as long as the first time from a fresh desktop session.
You have to understand QB64 has to translate BASIC code to C++ to then relay it to "g++" and other tools that comprise the GNU Compiler Collection ("gcc"). That takes time. If you take a short look at "(qb64pe)/internal/temp" directory, you will notice a few hundred text files which is the result of the translations. "(qb64pe)" is the directory where you installed QB64PE.
Each version of QB64 has compiled to executable slower than the previous, but because of the way the programming system has expanded. The Phoenix Edition v3 is more complex than Galleon's efforts before QB64 hit version 1. There are many more programs involved in the creation of executables, and perhaps some Python and some other interpreter. Before v0.98 on Windows, a bunch of DLL files were required pre-installed so the user executable could run. Now everything that is needed by the executable is packed into it which increases compilation and linking time. But computers these days have plenty of RAM, and if nothing else really heavy is being done by another program or by one written with QB64 then the wait shouldn't be as long as the first time from a fresh desktop session.