From: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: RE: BBLAYERS
Date: Tue, 4 Jan 2022 19:35:24 +0000 [thread overview]
Message-ID: <20220104193633.2F4CCC433F5@smtp.lore.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
Is it possible to use BBMASK to remove from builds ?
From: Monsees, Steven C (US)
Sent: Tuesday, January 4, 2022 2:32 PM
To: 'yocto@lists.yoctoproject.org' <yocto@lists.yoctoproject.org>
Subject: RE: BBLAYERS
Any suggestions... ?
From: Monsees, Steven C (US)
Sent: Tuesday, January 4, 2022 7:22 AM
To: yocto@lists.yoctoproject.org<mailto:yocto@lists.yoctoproject.org>
Subject: BBLAYERS
Under my Yocto build, I have basically 2 build directories (one for Arm and one for Intel platforms)... each build directory has its own bblayer.conf.
Under each of these directories I build multiple images for each platform...
If say, on the Intel side, I can build for 3 MACHINES creating 3 unique kernel images A, B, and C (they all share a common bblayer.conf) and I then want to modify one kernel to include meta-virtualization...
How would I manage the bblayer.conf to add this layer to only B's build so as not to impact the building of "A" or "C" ?
If I just add it to the common bblayer.conf, "A" and "C" are impacted by the addition and show:
WARNING: You have included the meta-virtualization layer, but 'virtualization' has not been enabled in your DISTRO_FEATURES. Some bbappend files may not take effect. See the meta-virtualization README for details on enabling virtualization support.
Thanks,
Steve
[-- Attachment #2: Type: text/html, Size: 4966 bytes --]
next reply other threads:[~2022-01-04 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 19:35 Monsees, Steven C (US) [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-04 19:32 BBLAYERS Monsees, Steven C (US)
2022-01-04 12:21 BBLAYERS Monsees, Steven C (US)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220104193633.2F4CCC433F5@smtp.lore.kernel.org \
--to=steven.monsees@baesystems.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.