From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] support/scripts/genimage.sh: allow setting rootpath from parameters.
Date: Wed, 18 Sep 2019 10:42:23 +0200 [thread overview]
Message-ID: <20190918104223.2222432b@windsurf> (raw)
In-Reply-To: <20190903120951.3318-1-raphael.melotte@essensium.com>
Hello Raphael,
On Tue, 3 Sep 2019 14:09:51 +0200
raphael.melotte at essensium.com wrote:
> From: Rapha?l M?lotte <raphael.melotte@essensium.com>
>
> Previously the rootpath was always set to $TARGET_DIR.
> This patch allows using other directories as rootpath.
>
> When you use genimage's mountpoints to generate an image with
> multiple (non-empty) partitions, it does two things:
> - copy $TARGET_DIR to $GENIMAGE_TMP/root
> - move any mountpoint from GENIMAGE_TMP/root to $GENIMAGE_TMP/<mountpoint>
>
> If you want to have an additional partition besides the rootfs, you
> will have to make sure it's content is in $TARGET_DIR so that genimage
> can find it.
>
> If you also use rootfs generated by buildroot, you will end up
> with two copies of the mountpoint: once in the rootfs itself, and once
> in the partition using the mountpoint.
Thanks for your contribution. While I understand the issue, I am not
sure we want to extend support/scripts/genimage.sh for this.
support/scripts/genimage.sh is meant to be a simple wrapper to
genimage, for the simple cases.
For the more complicated cases, your post-image script should call the
genimage tool directly. support/scripts/genimage.sh was only added in
Buildroot to avoid duplicating for our zillion defconfigs the same
logic over and over again. I don't think it should be extended to cover
more complicated cases: such complicated cases should call genimage
directly.
Arnout, Peter, any feedback on this ? I see that Raphael works at
Essensium, so I would imagine that perhaps this contribution has been
discussed with you Arnout before it was posted ? Or maybe not.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-18 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 12:09 [Buildroot] [PATCH 1/1] support/scripts/genimage.sh: allow setting rootpath from parameters raphael.melotte at essensium.com
2019-09-18 8:42 ` Thomas Petazzoni [this message]
2019-09-22 0:55 ` Carlos Santos
2019-09-22 7:01 ` Thomas Petazzoni
2019-09-23 7:44 ` Raphaël Mélotte
2019-09-23 7:55 ` Arnout Vandecappelle
2020-01-06 20:56 ` Thomas Petazzoni
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=20190918104223.2222432b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.