A .exe file pops up in the qb64 directory when running a code

[mrhuman]

Some .exe with the .bas file name comes. Is there anyway to automatically delete that when I close qb64? Please tell me as I am very storage space conscious and that file(though only a few kbs) takes up space. Or is there any setting to change so that the code only comes up in a console like q basic 4.5?

[STxAxTIC]

Hm, I never thought about a "delete EXE on exit" feature. Kinda profound...

Is it a matter of clutter in your qb64 folder? Or are you actually keeping track of every last kilobyte on the drive?

[bplus]

Welcome to the forum mrhuman.

I have sorta wished for a delete exe when I am backing up my bas code, the exe's are huge in comparison. I used to keep many backups on one storage disk. Now I have to delete old backups to make room for new, because of exes.

Yeah a simple program could do that for me ;-)) just copy all the files except the exes.

[mrhuman]

@STxAxTIC
Umm. For both the reasins
I have a lot of apps that hog up space(like adobe animate) so every kB is a lot of storage
As soon as the storage indicator in explorer turns red , I panick like something .

[mrhuman]

@bplus 
But the exe come in the qb64 folder

If you open the qb64 folder in one side and qb64 in the other and run a program, an exe comes in the folder.
I am asking for a script or something like that to delete them when qb64 is closed or the program is done testing.

[bplus]

@bplus 
But the exe come in the qb64 folder

If you open the qb64 folder in one side and qb64 in the other and run a program, an exe comes in the folder.
I am asking for a script or something like that to delete them when qb64 is closed or the program is done testing.

RE: reasons to get rid of an exe
Yes, I was just talking about my desire to save space when backing up.

RE: reasons to keep an exe
The exe's are handy in my work folders for me, to remind what the heck I was doing without having to load the code back up in the IDE. The exe's are handy for distinguishing version differences I have, again without having to reload the bas code and Run through IDE.  True kind of expensive space wise but now days there is no concern of me loading up my hard drive, ever!

[mrhuman]

@bplus
Oh

Still is it possible to add a feature in the run area something like this...

Run

Create an exe and run
Run in console
Create an exe

[FellippeHeitor]

Hello. Because QB64 is a compiler, you will always get an .exe file when you run a program, because it's the only way to run it. If you close the exe, make changes and run again, QB64 will overwrite the existing exe. Deleting it after run would be highly invasive, and generating an .exe every time you wanna run a program that didn't have changes would be counterproductive.

[bplus]

Doesn't it also save a little time (compiling) if an exe is already there?

[mrhuman]

But it just overwrites it.
So the same time is taken
I had made some code
Run it
Edited it
And ran in again
It took the same time

[STxAxTIC]

Delete after run (the exe) vs. delete after close (qb64.exe) though. But this is just choosing pink vs purple lipstick for a piggish idea. I'm done.

(EDIT: Because what if we're compiling qb64.bas itself?! Mind blown. (Don't take me seriously.))

What I think mrhuman should consider is getting a bigger hard drive.

[mrhuman]

Ok then ,no delete
But about adding a test in console ? That’s a good idea right?

[mrhuman]

Then there should be no worries about the auto delete thing. Right @STxAxTIC ?

[STxAxTIC]

I think deleting anything automatically is a pretty bad idea. This should be done manually. If you don't want to do it by hand each time, maybe write a little shell script to clear a folder of *.exe, and then only boot qb64 using that script.

Another idea: Never load a file directly. Only copy the code, and then paste it into the IDE. Then your exe will always be untitled, and you won't get a bunch of copies of it.

[mrhuman]

@STxAxTIC
Let’s just forget about the delete thing.
Adding a test in console or run in console could be considered