adjustable "compile to folder" path

Got an idea for enhancing PureBasic? New command(s) you'd like to see?
Axolotl
Addict
Addict
Posts: 893
Joined: Wed Dec 31, 2008 3:36 pm

adjustable "compile to folder" path

Post by Axolotl »

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
Just because it worked doesn't mean it works.
PureBasic 6.04 (x86) and <latest stable version and current alpha/beta> (x64) on Windows 11 Home. Now started with Linux (VM: Ubuntu 22.04).
User avatar
charvista
Addict
Addict
Posts: 949
Joined: Tue Sep 23, 2008 11:38 pm
Location: Belgium

Re: adjustable "compile to folder" path

Post by charvista »

+1
- Windows 11 Home 64-bit
- PureBasic 6.10 LTS (x64)
- 64 Gb RAM
- 13th Gen Intel(R) Core(TM) i9-13900K 3.00 GHz
- 5K monitor with DPI @ 200%
Randy Walker
Addict
Addict
Posts: 1170
Joined: Sun Jul 25, 2004 4:21 pm
Location: USoA
Contact:

Re: adjustable "compile to folder" path

Post by Randy Walker »

Axolotl wrote: Tue May 24, 2022 2:13 pm 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...)
viewtopic.php?p=571454
viewtopic.php?p=578330
Yes, Ditto that. It would certainly help with security concerns too.
- - - - - - - - - - - - - - - -
Randy
I *never* claimed to be a programmer.
User avatar
le_magn
Enthusiast
Enthusiast
Posts: 290
Joined: Wed Aug 24, 2005 12:11 pm
Location: Italia

Re: adjustable "compile to folder" path

Post by le_magn »

+1
Image
Post Reply