On 20 August 2017 at 02:19, Schmitt, Richard <[email protected]> wrote: > Hi, > > > > We were hoping to gather some information about our image by looking at the > image manifest files that are stored in the image/deploy directory alongside > our actual images. When I looked at these files, they were all empty for > all our different images. > > > > I had noticed that if we build using a non-multilib target machine, we do > end up with populated manifests so I assume it has something to do with > multilib. > > > > Has anyone else noticed this? I’m not sure if this is a xilinx issue or a > general yocto issue (I suspect the latter) but since we are building for the > zynqmp, I figured I’d start here.
I tested multilib for zynqmp with a lib32 target on oe & meta-xilinx master, and this appears to work fine. The image manifest contained both libc's for example: lib32-libc6 armv7vehf-neon-vfpv4 2.26-r0 libc6 aarch64 2.26-r0 What version are you using? The issue might have been resolved in oe since then, as the meta-xilinx layer doesn't need to do anything to enable or support multilib. Regards, Nathan -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
