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

I know it doesn't really answer the question, but why don't you remove
pulseaudio at the point where it is set, which is your distro config?

Alex

On Thu, 17 Oct 2024 at 17:22, jayson.k.mendoza via
lists.yoctoproject.org
<[email protected]> 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?
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#13454): https://lists.yoctoproject.org/g/poky/message/13454
> Mute This Topic: https://lists.yoctoproject.org/mt/109065659/1686489
> Group Owner: [email protected]
> Unsubscribe: https://lists.yoctoproject.org/g/poky/unsub [[email protected]]
> -=-=-=-=-=-=-=-=-=-=-=-
>