Interesting! Do I understand correctly that these are like manifests, but work for cross-compilation contexts? So that `gcc` would be linked to a gcc-arm-none-eabi, and the needed libraries also ready to use/link against for the specified architecture?
So, kind of like a `guix shell -D u-boot --target=riscv64-linux-gnu`, so I can manually build some kernel, bootloader or other software with the same tooling a `guix build --target=foo u-boot` would? I currently used manifests like so: --8<---------------cut here---------------start------------->8--- (define arm-toolchain (make-arm-none-eabi-toolchain-12.3.rel1)) --8<---------------cut here---------------end--------------->8--- but only to a rather limited degree. How can I use/try your code?
