On 6/30/23 07:45, Tulio Magno Quites Machado Filho wrote:
Kevin Kofler via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> writes:
Carlos O'Donell wrote:
And assembling those sysroots is not straight forward.
The easiest way is to unpack a live image. If you are targeting an Arch-
based or similar distro, you will probably get away with just unpacking the
image, because it installs development files by default. But if you are
targeting Fedora or a similar distro, you will probably want to compose a
custom live image with a bunch of -devel packages. (You can also try to
install packages within the sysroot, but if you are cross-compiling to a
different architecture, that is not straightforward, you either need to use
host tools and point them to the sysroot, or to use CPU emulation to run the
tools within the sysroot, or as a last resort to unpack package contents
manually.)
Containers might also help, e.g.:
podman run -it --rm \
--mount=type=image,source=fedora:38-ppc64le,destination=/sysroot \
fedora:38-x86_64 bash
The user still needs to compose both images with the required packages,
but it might be easier to keep them up-to-date.
I have been experimenting with creating sysroots with containers, and I
did something similar to this:
https://github.com/tstellar/fedora-cross-toolchain/blob/main/Dockerfile.cross
-Tom
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
