On Mon, Oct 26, 2015 at 9:31 AM, Jonathan Liu <net...@gmail.com> wrote: > On 26/10/2015 10:28 PM, Otavio Salvador wrote: >> On Mon, Oct 26, 2015 at 6:24 AM, Jonathan Liu <net...@gmail.com> wrote: >>> On 26/10/2015 7:08 PM, Paul Eggleton wrote: >>> It would rebuild qtbase (and recipes depending on it) without Raspberry >>> Pi >>> support for other machines. >>> I see similar machine-specific do_configure_prepend elsewhere (e.g. >>> >>> https://github.com/Freescale/meta-fsl-arm/blob/master/qt5-layer/recipes-qt/qt5/qtbase_%25.bbappend). >>> >>> Otavio, any thoughts on a better way to handle this? >> >> We handle this moving it to a SoC subarch and using a dynamic package >> arch handler to put every package depending on it as a subarch as >> well. Ideally we could split the QPA module and build it separated. No >> clue if it is possible or not. > > So for meta-fsl-arm, would only the qtbase-plugins package be using > machine-specific arch and the other qtbase packages be using > non-machine-specific arch? > Or is it done on a per-recipe rather than per-package granularity?
We have the handler, which allows for it to be done properly[1]. 1. http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/conf/machine/include/imx-base.inc#n68 Including 'qtbase' here will make it to move all packages depending on it for the subarch. The real long term solution is to try to split it and make the QPA package machine specific. I don't know if it is possible. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
