From: "Joshua Watt" <JPEWhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Joshua Watt <JPEWhacker@gmail.com>
Subject: [OE-core][PATCH v3 0/8] Add support for per-multiconfig BBMASK
Date: Tue, 2 Jun 2020 21:53:57 -0500 [thread overview]
Message-ID: <20200603025405.26885-1-JPEWhacker@gmail.com> (raw)
In-Reply-To: <20200601202807.26357-1-JPEWhacker@gmail.com>
Splits apart the bitbake configuration data and caches so that each
defined multiconfig can specify as separate BBMASK independently of the
other multiconfigs. This can take multiple forms, such as a `BBMASK` in
a multiconfig .conf file, or BBMASK assignment based on an override (see
linked bugzilla for an example).
The most noticeable change is that bitbake now keeps a parsing cache
file for each multiconfig instead of a single parsing cache file that
caches all multiconfigs.
V2: Fixes some syntax errors in tinfoil
V3: Optimizes caches so that each one only caches the files for it's own
multiconfig
Joshua Watt (8):
bitbake: cooker: Split file collections per multiconfig
bitbake: cache: Use multiconfig aware caches
bitbake: lib: Add support for Logging Adapters
bitbake: lib: Add PrefixLoggerAdapter helper
bitbake: cache: Improve logging
bitbake: cache: Cache size optimization
bitbake: tests: Add tests for BBMASK in multiconfig
bitbake: command: Move split_mc_pn to runqueue
bitbake/lib/bb/__init__.py | 30 ++-
bitbake/lib/bb/cache.py | 228 ++++++++++++------
bitbake/lib/bb/command.py | 39 +--
bitbake/lib/bb/cooker.py | 159 +++++++-----
bitbake/lib/bb/runqueue.py | 17 +-
.../bb/tests/runqueue-tests/conf/bitbake.conf | 3 +-
.../runqueue-tests/conf/multiconfig/mc1.conf | 1 +
.../runqueue-tests/conf/multiconfig/mc2.conf | 1 +
.../recipes/fails-mc/fails-mc1.bb | 5 +
.../recipes/fails-mc/fails-mc2.bb | 4 +
bitbake/lib/bb/tests/runqueue.py | 15 ++
bitbake/lib/bb/tinfoil.py | 26 +-
bitbake/lib/bblayers/query.py | 4 +-
13 files changed, 360 insertions(+), 172 deletions(-)
create mode 100644 bitbake/lib/bb/tests/runqueue-tests/recipes/fails-mc/fails-mc1.bb
create mode 100644 bitbake/lib/bb/tests/runqueue-tests/recipes/fails-mc/fails-mc2.bb
--
2.26.2
next parent reply other threads:[~2020-06-03 2:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200601202807.26357-1-JPEWhacker@gmail.com>
2020-06-03 2:53 ` Joshua Watt [this message]
2020-06-03 2:53 ` [OE-core][PATCH v3 1/8] bitbake: cooker: Split file collections per multiconfig Joshua Watt
2020-06-03 2:53 ` [OE-core][PATCH v3 2/8] bitbake: cache: Use multiconfig aware caches Joshua Watt
2020-06-03 2:54 ` [OE-core][PATCH v3 3/8] bitbake: lib: Add support for Logging Adapters Joshua Watt
2020-06-03 2:54 ` [OE-core][PATCH v3 4/8] bitbake: lib: Add PrefixLoggerAdapter helper Joshua Watt
2020-06-04 21:00 ` Richard Purdie
2020-06-03 2:54 ` [OE-core][PATCH v3 5/8] bitbake: cache: Improve logging Joshua Watt
2020-06-03 2:54 ` [OE-core][PATCH v3 6/8] bitbake: cache: Cache size optimization Joshua Watt
2020-06-03 2:54 ` [OE-core][PATCH v3 7/8] bitbake: tests: Add tests for BBMASK in multiconfig Joshua Watt
2020-06-03 2:54 ` [OE-core][PATCH v3 8/8] bitbake: command: Move split_mc_pn to runqueue Joshua Watt
2020-06-03 3:02 ` ✗ patchtest: failure for Add support for per-multiconfig BBMASK Patchwork
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=20200603025405.26885-1-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox