03-06-2024, 11:18 PM
Sorry, the responses came in too fast 
I was wondering about the second instance thing, since you have `temp2`, but that is 'supposed' to work and each compile mostly separate. The second instance will create a new `./internal/temp2` folder to compile into (as it did). On the naming of the executable I'm not really sure if it's supposed to produce `untitled2` or just regular `untitled`, maybe there's a mismatch in there somewhere and that's why it thinks the executable is not there (since clearly it compiled `untitled`, not `untitiled2`) 
If you give the source a name then that should resolve the issue and allow you to use multiple instances since they won't be trying to use the same executable name. If you don't need multiple instances though it's best to just avoid it.
I was wondering about the second instance thing, since you have `temp2`, but that is 'supposed' to work and each compile mostly separate. The second instance will create a new `./internal/temp2` folder to compile into (as it did). On the naming of the executable I'm not really sure if it's supposed to produce `untitled2` or just regular `untitled`, maybe there's a mismatch in there somewhere and that's why it thinks the executable is not there (since clearly it compiled `untitled`, not `untitiled2`) If you give the source a name then that should resolve the issue and allow you to use multiple instances since they won't be trying to use the same executable name. If you don't need multiple instances though it's best to just avoid it.