Re: [poky] Multiconfig Build using local.conf and multiconfig by design or bug?

On Thu, 2024-10-17 at 08:22 -0700, jayson.k.mendoza via
lists.yoctoproject.org wrote:
> Good Morning,
>  
> In my current project I was debugging why some DISTRO_FEATURE was
> missing from my environment when I used an multiconfig target in my
> build. When I checked the record in bitbake -e mc:mymulticonfig:core-
> image-weston I noticed that a DISTRO_FEATURE removed in the default
> local.conf build was applied to mymulticonfig's configuration. 
>  
> The lines in question that someone had in the local.conf were.
> ```
> DISTRO_FEATURES:remove = " pulseaudio"
> MACHINE_FATURES:remove = " pulseaudio"
> ```
>  
> Now I am aware this is flawed in the current version since pulseaudio
> and if I wanted to do that it should be added to
> DISTRO_FEATURES_BACKFILLED_CONSIDERED. However, I am interested to
> know why it even impacted my build at all. From documentation it's my
> understanding that local.conf is not used aside from the
> BBMULTICONFIG settings. It shouldn't have affected the global
> configuration which should be sourced from mymulticonfig.conf at 
> build/conf/multiconfig/mymulticonfig.conf. 
>  
> Is the local.conf supposed to be used by all multiconfigs?
> 

Yes, it is supposed to be used by all of them. It is included by a line
in bitbake.conf and the multiconfigs don't change that.

Cheers,

Richard