05-02-2022, 09:15 AM
** Aren't you over complicating things a bit?
i reexamined the source code of qb64. if the path of internal and temp had been coded in global variables at the beginning of the code, the modification would be easy. this is not the case. these references are found everywhere in the code of qb64. you are right SMcNeill. it would be complicated. that said, it would be a plus for qb64 as i have indicated in my other posts...
** As far as I know, all you'd need to do is copy your QB64 folder completely over your ramdrive, and then just run the QB64.exe from there. (Or download the proper package for your OS and then extract and set it up there.)
already done. i found that compilations are much faster. but it is not a practical solution...
** QB64 has been usable by command line for ages, and you can specify both the path for the infile and the outfile with it.
I know. But it has nothing to do with my suggestion.
** Also, as a workaround you might be able to turn the `./internal/temp` directory into a symlink to a location on your ramdisk. Not an ideal solution, but I think it would get you most of the way there without needing to wait for changes to QB64.
yes i have considered this solution DSMan195276. with a bash script. thanks for supporting the idea of managing a ramdisk. i still think it would be a plus for qb64. compiling programs is very slow on a mechanical hard disk. it got better when copying qb64 to ssd...
i reexamined the source code of qb64. if the path of internal and temp had been coded in global variables at the beginning of the code, the modification would be easy. this is not the case. these references are found everywhere in the code of qb64. you are right SMcNeill. it would be complicated. that said, it would be a plus for qb64 as i have indicated in my other posts...
** As far as I know, all you'd need to do is copy your QB64 folder completely over your ramdrive, and then just run the QB64.exe from there. (Or download the proper package for your OS and then extract and set it up there.)
already done. i found that compilations are much faster. but it is not a practical solution...
** QB64 has been usable by command line for ages, and you can specify both the path for the infile and the outfile with it.
I know. But it has nothing to do with my suggestion.
** Also, as a workaround you might be able to turn the `./internal/temp` directory into a symlink to a location on your ramdisk. Not an ideal solution, but I think it would get you most of the way there without needing to wait for changes to QB64.
yes i have considered this solution DSMan195276. with a bash script. thanks for supporting the idea of managing a ramdisk. i still think it would be a plus for qb64. compiling programs is very slow on a mechanical hard disk. it got better when copying qb64 to ssd...