On 16-07-19 18:32, Jean-Francois Dagenais wrote: > Hi Mike, > >> On Jul 16, 2019, at 01:38, Mike Looijmans <mike.looijm...@topic.nl> wrote: >> >> This should not work, IMAGE_FEATURES is only valid in the image recipe and >> won't be (fully) visible outside that. >> > > Indeed. It seems I have worked around the problem a little fast and thought > my solution was useable by others. > >> I frequently build multiple images in a single bitbake run where one is >> read-only and the other is not, e.g.: "bitbake my-image-sdcard >> my-image-norflash" > > Did you have any recipe(s) included in the read-only image which had the > update-alternative inheritance? If so, how did you make it work? My do_rootfs > fails saying it cannot complete the postinst steps for libmali-xlnx because > of the RO rootfs. >
Never encountered any problems with that, and there are quite a few alternatives for busybox for example. > In any case, I will probably not pursue this much further. For me, as I said > before, for most embedded systems, a choice is made as to what the drawing > backend will be (X11, wayland or fbdev) for the system, and only one version > is needed/wanted. So since I already maintain a fork of meta-xilinx, I will > simply clean out the update-alternative stuff from libmali-xlnx. > > Any thoughts? > Maybe there's something funky in the recipe that triggers bad behaviour in update-alternatives? -- _______________________________________________ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
