From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [PATCH v5 1/5] meta/image.bbclass: add image_do_mounts for image specific mounts
Date: Mon, 11 Feb 2019 10:09:17 +0100 [thread overview]
Message-ID: <20190211090921.9294-2-claudius.heine.ext@siemens.com> (raw)
In-Reply-To: <20190211090921.9294-1-claudius.heine.ext@siemens.com>
From: Claudius Heine <ch@denx.de>
Signed-off-by: Claudius Heine <ch@denx.de>
---
meta/classes/image.bbclass | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index d8fbfd5..bec62cd 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -14,6 +14,27 @@ IMAGE_FULLNAME = "${PN}-${DISTRO}-${MACHINE}"
KERNEL_IMAGE ?= "${@get_image_name(d, 'vmlinuz')[1]}"
INITRD_IMAGE ?= "${@get_image_name(d, 'initrd.img')[1]}"
+# Useful variables for imager implementations:
+PP = "/home/builder/${PN}"
+PP_DEPLOY = "${PP}/deploy"
+PP_ROOTFS = "${PP}/rootfs"
+PP_WORK = "${PP}/work"
+
+BUILDROOT = "${BUILDCHROOT_DIR}${PP}"
+BUILDROOT_DEPLOY = "${BUILDCHROOT_DIR}${PP_DEPLOY}"
+BUILDROOT_ROOTFS = "${BUILDCHROOT_DIR}${PP_ROOTFS}"
+BUILDROOT_WORK = "${BUILDCHROOT_DIR}${PP_WORK}"
+
+image_do_mounts() {
+ sudo flock ${MOUNT_LOCKFILE} -c ' \
+ mkdir -p "${BUILDROOT_DEPLOY}" "${BUILDROOT_ROOTFS}" "${BUILDROOT_WORK}"
+ mount --bind "${DEPLOY_DIR_IMAGE}" "${BUILDROOT_DEPLOY}"
+ mount --bind "${IMAGE_ROOTFS}" "${BUILDROOT_ROOTFS}"
+ mount --bind "${WORKDIR}" "${BUILDROOT_WORK}"
+ '
+ buildchroot_do_mounts
+}
+
inherit ${IMAGE_TYPE}
# Extra space for rootfs in MB
--
2.20.1
next prev parent reply other threads:[~2019-02-11 9:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 9:09 [PATCH v5 0/5] UBI support claudius.heine.ext
2019-02-11 9:09 ` claudius.heine.ext [this message]
2019-02-11 10:49 ` [PATCH v5 1/5] meta/image.bbclass: add image_do_mounts for image specific mounts chombourger
2019-02-11 11:33 ` Claudius Heine
2019-02-11 9:09 ` [PATCH v5 2/5] meta/classes: added ubifs-img class claudius.heine.ext
2019-02-11 9:09 ` [PATCH v5 3/5] meta/classes: added ubi-img class claudius.heine.ext
2019-02-11 9:09 ` [PATCH v5 4/5] meta/classes: added fit-img class for creation of fit images claudius.heine.ext
2019-02-11 9:09 ` [PATCH v5 5/5] meta-isar: added nand-ubi-demo example to demonstrate UBI use claudius.heine.ext
2019-02-11 9:45 ` [PATCH v5 0/5] UBI support Henning Schild
2019-02-12 11:24 ` Maxim Yu. Osipov
2019-02-12 13:16 ` Claudius Heine
2019-02-12 13:35 ` Claudius Heine
2019-02-12 13:36 ` Maxim Yu. Osipov
2019-02-12 14:06 ` Maxim Yu. Osipov
2019-02-12 14:09 ` Claudius Heine
2019-02-12 14:36 ` Baurzhan Ismagulov
2019-02-12 14:56 ` Claudius Heine
2019-02-12 15:51 ` Claudius Heine
2019-02-12 16:36 ` Claudius Heine
2019-02-13 8:36 ` Maxim Yu. Osipov
2019-02-13 9:53 ` Claudius Heine
2019-02-15 14:47 ` Maxim Yu. Osipov
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=20190211090921.9294-2-claudius.heine.ext@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=ch@denx.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