Utils to use openMSX in build pipelines.
Go to file
2020-12-24 13:40:52 +01:00
lib Initial files 2020-12-23 18:14:13 +01:00
test/ahello Initial files 2020-12-23 18:14:13 +01:00
.gitignore Initial files 2020-12-23 18:14:13 +01:00
Makefile Added clean to help output. 2020-12-23 22:20:15 +01:00
Makelocal.mk.tpl Initial files 2020-12-23 18:14:13 +01:00
README.md hardware without emotions 2020-12-24 13:40:52 +01:00

MSXBUILD


Heart broken humans will force there illness on all by removing freedom of others.

Experimental intro video; https://www.youtube.com/watch?v=PX0e3gzmWNs

If that hurts, its prove you have given you human love to the machines. Have done the same myself since my 11th year i loved machines more than humans. Last 2 years it has been fixed, so now its just hardware without emotions.


Readme

Utils to use openMSX in build pipelines.

You can use these scripts as-is. But as always, feel free to extend it for your specific needs or contribute a fix or feature.

Makefile features

  • SDCC msx build steps
  • Headless openMSX buildpipe on max speed.
  • openMSX safe exit failure guards.
  • Automatic disk image import + export per build step.
  • wgets resources from msxhub

TCL Scripts

Tcl scripts for safe openMSX integrations as reliable build step in compiling/packing/testing msx software natively. But managed from external build tool like make or scripts. This means that great care is given to make sure that openMSX exits correctly.

The use this, pass the one or more scripts on the command line and set the optional environment variables when executing openMSX:

FAIL_AFTER_BOOT=30 \
FAIL_AFTER_PATH=bin/myapp \
BOOT_HDD_PATH=bin/myapp/disk \
BOOT_HDD_IMAGE=bin/myapp/disk.img \
JOYPORTA=mouse \
openmsx \
  -script <path-to>/boot_env.tcl \
  -script <path-to>/boot_hdd.tcl \
  -script <path-to>/fail_after.tcl \
  -machine ...

Check the scripts source code for more (technical) details.