-
Notifications
You must be signed in to change notification settings - Fork 68
Development with
jsbeeb can be efficiently included in your build cycle as follows. This shows a example using BeebAsm, but any build script that can output an .ssd
file can be made to work.
Setup a local installation of jsbeeb with a clone of the repo (e.g. to C:\workspace\bbc\jsbeeb
), and then run a local webserver.
C:\workspace\bbc> cd jsbeeb
C:\workspace\bbc\jsbeeb> python -m http.server
Serving HTTP on :: port 8000 (http://[::]:8000/) ...
Test that jsbeeb is running - launch http://localhost:8000
.
jsbeeb can load a disc image from its local discs
folder, e.g. C:\workspace\BBC\jsbeeb\discs
, with the parameter disc1=image.ssd
and will boot from that disc with the autoboot
parameter.
So if working with beebasm then you can use a .cmd
file like this to build MYAPP, and copy the output to the jsbeeb folder.
..\beebasm-1.09\beebasm -i source.asm -do MYAPP.ssd -boot MYAPP
..\beebasm-1.09\beebasm.exe -vc -i source.asm -v > build_output.asm
copy MYAPP.ssd C:\workspace\BBC\jsbeeb\discs
Then run MYAPP as follows:
http://localhost:8000/?&about&keyLayout=natural&disc1=MYAPP.ssd&autoboot
Just refresh the page after each build to test the application.