You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
May I rather suggest the possibility to setup different toolchain scripts in the settings. For example, one may need to compile only, compile and run, maybe see the asm output, etc...
A good example is "Compile and run scripts" in Relaunch64. Here you can add your plans and choose which script to run.
The program may then be shipped with pre-set scripts, e. g. "Compile to DASM format", "Compile to .prg", "Compile and run", etc.
I'll plan to do this as an option. Not sure about scripts, though. In my idea you can specify in the (upcoming) project settings where you want the output to be created to. XC=BASIC just creates a .prg as usual, but after that the .prg might be moved into a .d64 or .crt - or just stays as a .prg. Compile (& Run) will always have the same functionality, and does the above tasks additionally.
Okay, it's up to you. Just to remember, the xcbasic64 executable outputs assembly code, while the xcb bash script (or xcb.bat on WIndows) creates the final .prg file. The former is useful for debugging purposes.
If the file is compiled successfully it'll copied onto a .d64 image.
The text was updated successfully, but these errors were encountered: