howto-wasm-minimal VS chip8-book

I'm particularly curious on what parts cheerp adds to their clang+llvm base. Presumably it's something like the C standard target library for WASM/JS?

For reference, here's examples of what you could do with the baseline clang with wasm (but not JS?) [1] [2] [3], referenced from a similar thread on HN.

[1] https://github.com/ern0/howto-wasm-minimal

[2] https://github.com/robrohan/wefx

[3] https://github.com/PetterS/clang-wasm

For future readers, this is the code that is being referred:

https://github.com/ern0/howto-wasm-minimal/blob/master/inc.c...

It should be:

   uint32_t gray = 0.299 * ptr[i] + 0.587 * ptr[i+1] + 0.114 * ptr[i+2];

This uses a strange "link broker", the link behind this is pointing to https://github.com/ern0/howto-wasm-minimal

Not to discourage you, but there's already a CHIP-8 book in progress: https://github.com/aquova/chip8-book

WASM support would be so cool. There are lots of guides online which could help you out. I saw a guide for the chip8 and it didn't even look too difficult, you can check it out here https://github.com/aquova/chip8-book

Recently I've decided to learn low level programming with Rust. I asked for some projects to practice and got recommened to make a Chip8 emulator. That sounded fun so I searched a bit and found this guide that walks you step by step.

I made some emulators in Rust as a learning project during the start of the pandemic, and ran into the exact same issue when I wanted to make a wasm version to run in a browser. Eventually, I was able to figure out how to do it, although I do use the 'wasm-pack' Cargo package to assist with it (I think you can get away without it if you're really motivated, you just need to set up the targets and other elements yourself). Basically you define some Rust API to expose whatever you need from your project, then that and the project get compiled into one .wasm binary and some (surprisingly readable) JavaScript "glue" gets generated which allows for easy inclusion into a web page. It works well for code in the std, but I've had issues with 3rd party packages.

It's focused on emulation development, but I wrote a document that describes the process I followed: https://github.com/aquova/chip8-book/blob/master/src/wasm.md

I followed [this](https://github.com/aquova/chip8-book) book which uses Rust.