Open laenzlinger opened 1 year ago
you can use qemu-user-static package to run these binaries on any system, or setup binfmt-support to do it automatically.
both dpf makefile and cmake already have ways to specify this.
under make you can use make EXE_WRAPPER="qemu-aarch64-static -L /path/to/toolchain/sysroot"
and cmake uses CMAKE_CROSSCOMPILING_EMULATOR
just set those accordingly if not wanting to deal with the binfmt stuff, which tends to need support from the outer layer of docker (ie, the host) so it is not always as easy to set up
note that whatever using elk or Pi, or ubuntu core or something else it does not matter. the procedure is always the same, and it is known to work everywhere I have tested so far.
thank you so much @falkTX
It worked like a charm when after installing qemu-user-static on the container with
sudo apt-get install qemu-user-static
and then building dragonfly-reverb with
make EXE_WRAPPER="qemu-aarch64-static -L /opt/elk/1.0.0/sysroots/cortexa72-elk-linux"
I am trying to cross-compile a plugin with DISTROH DPF
When the LV2 assets are built the following error happens"
Steps to reproduce
1) build the https://github.com/elk-audio/elk-audio-os-builder (see README) 2) run the docker docker container
docker run --name elk-cross-compiler -it elk-audio-os-builder
3) install the SDK https://github.com/elk-audio/elkpi-sdk4) activate the cross-compiler:
. /opt/elk/1.0.0/environment-setup-cortexa72-elk-linux
5) clone and build the pluginPotential problem
It looks like the the v2-ttl-generator is built with the cross compiler for the target platform and can then not be executed on the host platform.
I am not experienced in cross-compilation, therefore I wanted to ask what would be best practice to resolve this. Maybe this issue has to be solved on the plugin which is uses DPF (dragonfly-reverb)?