opam-cross-android VS dockcross

We use the add_executable command to build executables with itk-wasm. The Emscripten and WASI toolchains along with itk-wasm build and execution configurations are contained in itk-wasm dockcross Docker images invoked by the itk-wasm command line interface (CLI). Note that the same code can also be built and tested with native operating system toolchains. This is useful for development and debugging.

Docker is great for self-contained build environments, no risk of them breaking each other. Eg. https://github.com/dockcross/dockcross

It is C ++ 11 compatible, I recommend C ++ 17, it is cross-platform (x86, ARMv7, ARMv8, PowerPC, windows, Linux...), Thanks to [dockcross](https://github.com/dockcross/dockcross) .

First of all, I learned basic instructions of AArch64 and how to use cross compile COOL codes into AArch64 assembly codes via dockcross.

It is C ++ 11 compatible, I recommend C ++ 17, with OpenMP (For better multi-core performance), it is cross-platform (x86, ARMv7, ARMv8, PowerPC, windows, Linux...), Thanks to dockcross .

I would not say it easy, but checkout this setup: https://github.com/dockcross/dockcross

I still maintain a single LXC container for each service. So far I'm doing this to run Nginx Proxy Manager and Vaultwarden, as well as a development container where I use Docker to run cross-platform builds with dockcross.

xcross provides Docker images with toolchains for a wide variety of different architectures, C and C++ standard libraries, and both bare-metal and Linux-based systems. A complete list of supported targets can be found here. This differs from dockcross in that it supports numerous more architectures and C runtimes.