Re: [oe] Regarding poppler auto PACKAGECONFIG when qt5-layer exists

["Matthew" <matthew.zeng@windriver.com>]

Khem Raj <raj.khem@gmail.com> writes:

> On 4/1/20 1:28 PM, Matthew wrote:
>> Hello,
>> In meta-oe/recipes-support/poppler/poppler_0.85.0.bb line 17, there
>> is the line
>>      PACKAGECONFIG ??= "jpeg openjpeg png tiff nss
>> ${@bb.utils.contains('BBFILE_COLLECTIONS', 'qt5-layer', 'qt5', '',
>> d)}"
>> Let's say I add meta-qt5 to bblayers.conf, but I don't plan to use
>> it immediately in a build. Therefore I haven't make any additional
>> change to local.conf.
>> However I will be receiving the following error when starting a
>> build:
>>      WARNING: qtbase is not whitelisted, figuring out PNWHITELIST...
>>      ERROR: Nothing PROVIDES 'qtbase' (but .../meta-openembedded/meta-oe/recipes-support/poppler/poppler_0.85.0.bb DEPENDS on or otherwise requires it)
>> because PACKAGECONFIG is changed so it assumes I'll be using qt5. Is
>> this reasonable?
>>
>
> Yeah I think here the choice is dynamic, what happens if you add a
> bbappend where you do PACKAGECONFIG_remove = "qt5" does that work ?

Haven't test specifically, but this should work.

However I personally don't think it is reasonable to add a PACKAGECONFIG_remove line, or any line in local.conf for a layer that I don't plan to use immediately.
The layer is added to bblayers.conf because I can use it whenever I feel necessary for my build, but I don't think anything should be triggered based on bblayers.conf, it creates more confusion.

Matthew

>
>> --
>> Mingde (Matthew) Zeng
>>
>> 
>>


--
Mingde (Matthew) Zeng