Difference between revisions of "Guides:MAME - emscripten"
Jump to navigation
Jump to search
(Created page with "A set of notes on MAME - emscripten (0261) based on personal experience playing around with it, may bleed over into emularity notes * Build env in docker: https://github.com/...") |
|||
| Line 3: | Line 3: | ||
* Build env in docker: https://github.com/mameau/mame-emscripten-docker | * Build env in docker: https://github.com/mameau/mame-emscripten-docker | ||
* Build script: https://github.com/mameau/mame-build-emscripten | * Build script: https://github.com/mameau/mame-build-emscripten | ||
| + | |||
A successful build creates 3 files: js, wasm and html each are named after whatever you pass as SUBTARGET | A successful build creates 3 files: js, wasm and html each are named after whatever you pass as SUBTARGET | ||
Latest revision as of 04:24, 28 December 2023
A set of notes on MAME - emscripten (0261) based on personal experience playing around with it, may bleed over into emularity notes
- Build env in docker: https://github.com/mameau/mame-emscripten-docker
- Build script: https://github.com/mameau/mame-build-emscripten
A successful build creates 3 files: js, wasm and html each are named after whatever you pass as SUBTARGET
Note: The html isn't required for use with a loader like emularity
To upload roms you'll need to use the Web File API.
NVRAM does not appear to be supported at the moment as it relies on hard-reset which breaks the js version (at least with emularity)
Hard Reset isn't supported (might be an emularity thing)