emsdk VS CLI11

One place that I’ve found some real, open source unit tests to look at for an example is in the emsdk for emscripten: https://emscripten.org

Your default path was set by emsdk, given where the path is pointing. Your modified path is the path the installer linked in the Godot docs sets, just typically that kind of stuff doesn't override existing variables. This is a good thing to keep in mind in general as if you end up having to use a different version for something else in the future and just install it expecting the installer to update it for you, you will likely run into the same issue.

Emscipten C/C++ to WebAssembly compiler.

I am playing around with Emscipten which wraps around clang to compile C/C++ code in WASM binary and provide some glue-code API to embed WASM binary into JavaScript. Look into MDN Docs and Emscripten SDK to get started.

Elm is a different approach that compiles into JavaScript. In the extreme case, you have Emscripten which will compile many language into JavaScript but will feel really clumsy compared to using JavaScript in a lot of cases.

https://emscripten.org/ ?

SQLite is a pretty popular database and it's a critical dependency for many different applications. By compiling it to Wasm32-wasi, you can add it to any WebAssembly module.

This enables a new set of possibilities for Wasm and SQLite. For example, now you can run a full WordPress application in the browser [1][2] / server [3] using the same Wasm module. Note that for the browser these projects use Emscripten [4], but in the future the same Wasm32-wasi module will work.

In general, any environment that includes a wasm runtime can potentially run applications that uses SQLite under the hood. Before, it wasn't possible.

- [1] https://wordpress.wasmlabs.dev/

- [2] https://developer.wordpress.org/playground/demo/

- [3] https://wasmlabs.dev/articles/running-wordpress-with-mod-was...

- [4] https://emscripten.org/

The emscripten interface for the assimp library. It runs entirely in the browser, and allows you to import 40+ 3D file formats and access the result in JSON or glTF format. This is not a full port of assimp, but an easy to use interface to access it's functionality.

Three.js is written in JS and loads like a JS library on a modern website. Godot is a binary application transpiled to WASM (with the help of emscripten), resulting in a pretty large initial payload. Godot provides JS integration, but it feels less "native" with its layers of abstraction.

Book: CLI11 book

The most feature-rich C++ CLI library is CLI11. Other popular choices include Boost.ProgramOptions, argparse, cxxopts and others.

CLI11 provides all the features you expect in a powerful command line parser, with a beautiful, minimal syntax and no dependencies beyond C++11. itk-wasm enhances CLI11 with a itk::wasm::Pipeline wrapper to support efficient execution in multiple Wasm contexts, scientific data structures, and lovely colorized help output 🥰.

Does anyone have feedback on the possible problems with CLI11 and comparisons to any other thing available in the wild not limited to the choices I tried before? Looks like a very well-thought out library according to its documentation: https://cliutils.github.io/CLI11/book/

I'd recommend to use CLI11. I was baffled by how much it can do.

I use https://github.com/jarro2783/cxxopts.git or https://github.com/CLIUtils/CLI11, or if boost is involved anyway, boost.program_options.

get_dependency(spdlog "https://github.com/gabime/spdlog" v1.8.5) get_dependency(CLI11 "https://github.com/CLIUtils/CLI11" v1.9.1) get_dependency(GoogleTest "https://github.com/google/googletest" master)

Maybe https://github.com/CLIUtils/CLI11? I really like this one and it looks like it supports TOML

I found https://github.com/jarro2783/cxxopts to be useful and https://github.com/CLIUtils/CLI11 to be really helpful if you need an non-trivial interface.