From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v3 0/6] Support multiple image types in one build
Date: Fri, 19 Nov 2021 10:14:54 +0100 [thread overview]
Message-ID: <20211119091500.12341-1-ubely@ilbers.de> (raw)
Changed since v2:
- get back multiconfigs removed in v2/v1;
- mc:qemuamd64-buster now builds wic-img and ext4-img and doesn't
conflict with mc:qemuamd64--cpiogz and mc:qemuamd64--tgz;
- docs updated to fit new (array-like) meaning of the variable
IMAGE_TYPE (IMAGE_FSTYPES with last patch).
Changes since v1:
- removed mc:qemuamd64-buster-cpiogz config;
- mc:qemuamd64-buster config now includes cpiogz image type.
The patchset makes possible to build several image types for
the specific target by listing all them in IMG_FSTYPES variable.
This also deprecates using IMG_TYPE variable.
Actually, IMG_TYPE=>IMG_FSTYPES renaming is done just
to correspond Yocto/OE naming and is not mandatory.
So, the last patch in series may be omitted.
Uladzimir Bely (6):
image: Support multiple image types in WORKDIR and STAMPS
wic-img: Set weak default value for WKS_FILE
start_vm: Use the first image type to start VM
multiconfig: Add ext4-img type to qemuamd64-buster multiconfig.
doc: Update docs to fit new IMAGE_TYPE meaning
api: Rename IMAGE_TYPE to IMAGE_FSTYPES
RECIPE-API-CHANGELOG.md | 5 +++
doc/user_manual.md | 31 +++++++++++++------
meta-isar/conf/machine/bananapi.conf | 2 +-
meta-isar/conf/machine/container-amd64.conf | 2 +-
meta-isar/conf/machine/de0-nano-soc.conf | 2 +-
meta-isar/conf/machine/hikey.conf | 2 +-
meta-isar/conf/machine/nand-ubi-demo.conf | 2 +-
meta-isar/conf/machine/nanopi-neo.conf | 2 +-
meta-isar/conf/machine/qemuamd64.conf | 2 +-
meta-isar/conf/machine/qemuarm.conf | 2 +-
meta-isar/conf/machine/qemuarm64.conf | 2 +-
meta-isar/conf/machine/qemui386.conf | 2 +-
meta-isar/conf/machine/qemumipsel.conf | 2 +-
meta-isar/conf/machine/qemuriscv64.conf | 2 +-
meta-isar/conf/machine/rpi.conf | 2 +-
meta-isar/conf/machine/sifive-fu540.conf | 2 +-
meta-isar/conf/machine/stm32mp15x.conf | 2 +-
meta-isar/conf/machine/virtualbox.conf | 2 +-
meta-isar/conf/machine/vmware.conf | 2 +-
.../multiconfig/qemuamd64-buster-cpiogz.conf | 2 +-
.../multiconfig/qemuamd64-buster-tgz.conf | 2 +-
.../conf/multiconfig/qemuamd64-buster.conf | 2 ++
meta/classes/image.bbclass | 14 ++++++---
meta/classes/wic-img.bbclass | 2 ++
scripts/start_vm | 8 +++--
testsuite/start_vm.py | 2 +-
26 files changed, 65 insertions(+), 37 deletions(-)
--
2.20.1
next reply other threads:[~2021-11-19 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 9:14 Uladzimir Bely [this message]
2021-11-19 9:14 ` [PATCH v3 1/6] image: Support multiple image types in WORKDIR and STAMPS Uladzimir Bely
2021-11-19 9:14 ` [PATCH v3 2/6] wic-img: Set weak default value for WKS_FILE Uladzimir Bely
2021-11-19 9:14 ` [PATCH v3 3/6] start_vm: Use the first image type to start VM Uladzimir Bely
2021-11-19 9:14 ` [PATCH v3 4/6] multiconfig: Add ext4-img type to qemuamd64-buster multiconfig Uladzimir Bely
2021-11-19 9:14 ` [PATCH v3 5/6] doc: Update docs to fit new IMAGE_TYPE meaning Uladzimir Bely
2021-11-19 9:15 ` [PATCH v3 6/6] api: Rename IMAGE_TYPE to IMAGE_FSTYPES Uladzimir Bely
2021-12-01 13:24 ` [PATCH v3 0/6] Support multiple image types in one build Anton Mikanovich
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=20211119091500.12341-1-ubely@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
/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