Right away: I know that this has often been requested. As I find it useful, I renew the request here again.
A new environment variable for the "compile to folder" path would be a solid improvement.
Now PB does use the TEMP, TMP variables - with a slightly different naming depending on the platform. (since I only use Windows, this is a guess)
A new variable like PUREBASIC_TEMP or PUREBASIC_OUTPUT similar to PUREBASIC_HOME could help here?
Reason (compilation):
+ More flexibility by setting up a separate folder e.g. RAM disk (ideal for me, because I build only small tools).
+ The general switching of global Temp, Tmp directories unfortunately leads to undesirable side effects (other programs!).
+ To avert AV false positives, the folder can be added to the whitelist
+ The currently only alternative to TEMP ("Create temporary executable in the source directory") is not accepted by all. I for example don't want to mix my source folders with executables.
+ helps to save the ssd (one of my biggest fears is compiling the disk broken)
+ Many similar requests and notable supporters over the years
Thank you for knowledge and review.
See also other older requests on the topic: (I found this two, may be there are much more...)
https://www.purebasic.fr/english/viewtopic.php?p=571454
https://www.purebasic.fr/english/viewtopic.php?p=578330
adjustable "compile to folder" path
adjustable "compile to folder" path
Mostly running PureBasic <latest stable version and current alpha/beta> (x64) on Windows 11 Home