01-08-2023, 08:41 PM
(This post was last modified: 01-08-2023, 08:42 PM by mnrvovrfc.
Edit Reason: Fixed spelling mistakes
)
Some people have to be defended from "oopsie" which is common.
Start fiddling with compiler options and get burned "suddenly". Want those options for only one program. Then load another source code which was on the list which didn't need those options, or better yet, shouldn't have them, and after the program is compiled and run it crashes or hangs. WTF but it ran fine before?
That's why I have never touched "compiler options" with the QB64PE IDE. I don't think it makes a great difference, and those who seriously believe that it helps with tiny performance improvements, do the whole thing in C++ and forget about this product.
I mean, on Linux "qb64pe" executable doesn't need "make -j8" or something like that, which I was told to use by somebody else while I was trying to compile something which begged much more memory than I had available.
A solution is to have multiple QB64PE installations, each one with desired compiler options. Name the main directories to that effect if the user has to. Since you seem to be a pack-rat bplus, this might be worth a try, even if each install is at least 100MB on Windows...
If you're clever enough, create a program which stores certain groups of "recent.bin" and "config.ini" which are recalled by a short word, copied to their expected places before "qb64pe" executable is fired. Something on the command line like:
But this would be only for opening the IDE, not to create an executable from a terminal which is likely to beg more options such as -o and -x.
Start fiddling with compiler options and get burned "suddenly". Want those options for only one program. Then load another source code which was on the list which didn't need those options, or better yet, shouldn't have them, and after the program is compiled and run it crashes or hangs. WTF but it ran fine before?
That's why I have never touched "compiler options" with the QB64PE IDE. I don't think it makes a great difference, and those who seriously believe that it helps with tiny performance improvements, do the whole thing in C++ and forget about this product.
I mean, on Linux "qb64pe" executable doesn't need "make -j8" or something like that, which I was told to use by somebody else while I was trying to compile something which begged much more memory than I had available.
A solution is to have multiple QB64PE installations, each one with desired compiler options. Name the main directories to that effect if the user has to. Since you seem to be a pack-rat bplus, this might be worth a try, even if each install is at least 100MB on Windows...
If you're clever enough, create a program which stores certain groups of "recent.bin" and "config.ini" which are recalled by a short word, copied to their expected places before "qb64pe" executable is fired. Something on the command line like:
Code: (Select All)
myqb64pe.exe fastestBut this would be only for opening the IDE, not to create an executable from a terminal which is likely to beg more options such as -o and -x.