Qb64 is inherently broken (simple example)

Qb64 is inherently broken (simple example) - Printable Version

+- QB64 Phoenix Edition (https://qb64phoenix.com/forum)
+-- Forum: Chatting and Socializing (https://qb64phoenix.com/forum/forumdisplay.php?fid=11)
+--- Forum: General Discussion (https://qb64phoenix.com/forum/forumdisplay.php?fid=2)
+--- Thread: Qb64 is inherently broken (simple example) (/showthread.php?tid=2488)

Pages: 1 2

RE: Qb64 is inherently broken (simple example) - JamesAlexander - 03-06-2024

@Dsman: Yes, that was it. Thank you!
@SMcneill: Thank you

RE: Qb64 is inherently broken (simple example) - DSMan195276 - 03-06-2024

Sorry, the responses came in too fast Tongue

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`) Undecided

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.

RE: Qb64 is inherently broken (simple example) - Kernelpanic - 03-07-2024

On Windows there is no problem with multiple "untitled.bas" versions.