Re: [meta-xilinx] [PATCH] libmali-xlnx: inherit update-alternatives only on rw-rootfs builds

2019-07-18 Thread Mike Looijmans
On 16-07-19 18:32, Jean-Francois Dagenais wrote: > Hi Mike, > >> On Jul 16, 2019, at 01:38, Mike Looijmans 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

Re: [meta-xilinx] [PATCH] libmali-xlnx: inherit update-alternatives only on rw-rootfs builds

2019-07-16 Thread Jean-Francois Dagenais
Hi Mike, > On Jul 16, 2019, at 01:38, Mike Looijmans 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.

Re: [meta-xilinx] [PATCH] libmali-xlnx: inherit update-alternatives only on rw-rootfs builds

2019-07-15 Thread Mike Looijmans
This should not work, IMAGE_FEATURES is only valid in the image recipe and won't be (fully) visible outside that. 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" On 16-07-19 03:44, Jean-F

[meta-xilinx] [PATCH] libmali-xlnx: inherit update-alternatives only on rw-rootfs builds

2019-07-15 Thread Jean-Francois Dagenais
update-alternatives.bbclass adds a target-ran post-inst step which cannot work on RO rootfs systems. Thankfully an error was put in place in poky's base image class to detect this. With this patch, on these builds, the default lib (MALI_BACKEND_DEFAULT) prevails as the active library. Others may b