dockcross VS cross

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.

To compile a program with musl on a glibc system you can use cross-rs!

I cross compile to Mac, bsd, windows, etc cross ... Works great for me with either docker or podman.

If docker is available for you, https://github.com/cross-rs/cross is another and reliable way to solve this kind of problem. I do use it regularly.

We are using https://github.com/cross-rs/cross.

There is some built-in support in rustc for cross-compiling, but getting the build to actually work can be tricky due to the need for an appropriate linker. Instead, we’re going to use the Cross crate, which used to be maintained by the Rust Embedded Working Group Tools group.

I have used cross before to cross compile from Linux to other Linux. It has a section on it's wiki about this. Maybe that could be of help.

You can use cross to build your application and copy the artifacts into an alpine armv7 container. It would also build faster due to using cross compilation rather than QEMU.

Looks like cross is the easiest way to get something cross-compiled but its Mac support is blocked behind building your own build image. Even that repo says that it might be broken.

Bonus: if you’re working with Rust and doing a lot of cross platform stuff, check out cross. It runs QEMU in docker so you can run tests on a bunch of different emulated targets easily- literally a one line setup, it’s kind of magical.

It's also not as naturally cross-compilable as Go, though that's partly a side-effect of not accepting being a semi-closed ecosystem to achieve that and cross exists as a stop-gap while things like cargo-zigbuild explore less drastic options.