So I dug into this today, and as I suspected, there's currently not a
great way to inhibit the warning easily (it's broken).
I'm going to re-work some things and fix this in master .. it's
interesting that no one else has asked about this until now.
If you don't want to define your own BSP, my suggestion is to just
inhibit the warning with the KCONF_AUDIT_LEVEL and
KCONF_BSP_AUDIT_LEVEL variables. You know what you are doing with
those warnings, so they can be safely masked.
On Tue, Mar 17, 2020 at 10:22 PM Bruce Ashfield
> Thanks Fred,
> Let me fire up a build with this tomorrow and I'll follow up with the
> best thing to do.
> On Tue, Mar 17, 2020 at 9:07 PM Fred Baksik <fdk17@...> wrote:
> > What you are doing, is the right way to do things, unless you modify
> > the source fragment directly.
> > I used 'bitbake linux-intel -c menuconfig' and 'bitbake linux-intel -c diffconfig'. This generated a fragment that contained the single line:
> > # CONFIG_SOUND is not set
> > I added this fragment to my "recipes-kernel/linux/linux-intel_%.bbappend".
> > Can you send me the exact layers/branches you are using, and I'll
> > confirm the right thing to do with a local build.
> > I'm using warrior 2.7.3 and MACHINE=intel-corei7-64
> > poky
> > meta-intel
> > meta-openembedded
> > It was easy enough to remove items, like alsa, from DISTRO_FEATURES to remove the features I wouldn't need.
> > I had wanted to remove the items, like audio support, from an existing machine instead of creating one from scratch.
> > Thanks,
> > Fred