Hi Mark, Thanks for taking a look! Comments below.
> The primary usage is to build an external toolchain. The external toolchain > can be used to build baremetal but does NOT include libxil. libxil is tied > to the > hardware and is built 'elsewhere'. Yes, I should have mentioned, I started by generating a platform project using Vivado (feeding it a .xsa). I am converting the Makefile-based build system to Meson. So we are building libxil that way. > The external toolchain is built using: > > DISTRO=xilinx-standalone > MACHINE=aarch32-tc > > bitbake meta-toolchain > > Use the environment file for the correct output and use the matching libxil.a > and it should work. I think for Cortex R5, I'd want to use arm-rm-tc, right? (Since it's armv7-r) However, I will need aarch32-tc because we also are targeting a Zynq 7000. For that one, I think we need the armv7afpthf tune. Seems like the MACHINES are implemented using multilib, though. I don't really have any experience with that. Do you have any advice on how to use multilib for this? I am trying to dig up documentation on how to actually incorporate multilib into a build but it is sparse. (There is https://docs.yoctoproject.org/dev-manual/common-tasks.html#combining-multiple-versions-of-library-files-into-one-image but it didn't really help my understanding). I will also ask on the mailing list. > > You have to have libxil.a (which is analogous to libgloss) that describes the > hardware interfaces. Since the interfaces are configurable, there is no > default > libxil.a that I am aware of. (Possible one exists, I just don't know of that > part.) > Makes sense, thanks! Thanks again, Chris
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5094): https://lists.yoctoproject.org/g/meta-xilinx/message/5094 Mute This Topic: https://lists.yoctoproject.org/mt/95098230/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
