Hi Tom,
To re-iterate what others have already said: Thanks for driving Beeb-related VSCode extension development forward!
I currently use Simon's BeebVSC extension and I thought I would take a look to see if I could get your new version working with my current code. However am already hitting a few snags. I use a make-based build process that invokes BeebAsm multiple times over several different passes, and the files that are included in the build depends on which pass is being run. To make it even worse, both 6502 source, and binary blobs, from earlier passes are fed back into later ones, sometimes with other tools processing them in between.
Everything is done via a top-level "Main.6502" file. However I couldn't really work out how to get your extension working within that framework. I already have my tasks.vscode set up to run various shell scripts that invoke make, which runs BeebAsm, so I can't really 'add a BeebVSC target', which seems to be a central part of getting it all working.
I'm just wondering whether there might be any way to support this kind of multi-pass approach? I appreciate that it's probably not really the intended use-case.
Thanks!
To re-iterate what others have already said: Thanks for driving Beeb-related VSCode extension development forward!
I currently use Simon's BeebVSC extension and I thought I would take a look to see if I could get your new version working with my current code. However am already hitting a few snags. I use a make-based build process that invokes BeebAsm multiple times over several different passes, and the files that are included in the build depends on which pass is being run. To make it even worse, both 6502 source, and binary blobs, from earlier passes are fed back into later ones, sometimes with other tools processing them in between.
Everything is done via a top-level "Main.6502" file. However I couldn't really work out how to get your extension working within that framework. I already have my tasks.vscode set up to run various shell scripts that invoke make, which runs BeebAsm, so I can't really 'add a BeebVSC target', which seems to be a central part of getting it all working.
I'm just wondering whether there might be any way to support this kind of multi-pass approach? I appreciate that it's probably not really the intended use-case.
Thanks!
Statistics: Posted by VectorEyes — Sun Feb 04, 2024 11:17 pm