From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] rootfs-overlay: use a make foreach instead of a shell for
Date: Tue, 30 Apr 2013 18:59:00 +0200 [thread overview]
Message-ID: <517FF854.9090903@mind.be> (raw)
In-Reply-To: <1365439816-6935-4-git-send-email-luca@lucaceresoli.net>
On 08/04/13 18:50, Luca Ceresoli wrote:
> Makes the code uniform with the post-build and post-image implementation
> (which is slightly simpler and, presumably, more efficient).
>
> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
I thought about the possibility to refactor these three use cases into
a single make function, but it would actually just complicate things.
Regards,
Arnout
> ---
> Makefile | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index f475d1b..a3b98f3 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -501,13 +501,12 @@ endif
> echo "PRETTY_NAME=\"Buildroot $(BR2_VERSION)\"" \
> ) > $(TARGET_DIR)/etc/os-release
>
> - @for dir in $(call qstrip,$(BR2_ROOTFS_OVERLAY)); do \
> - $(call MESSAGE,"Copying overlay $${dir}"); \
> + @$(foreach d, $(call qstrip,$(BR2_ROOTFS_OVERLAY)), \
> + $(call MESSAGE,"Copying overlay $(d)"); \
> rsync -a \
> --exclude .empty --exclude .svn --exclude .git \
> --exclude .hg --exclude '*~' \
> - $${dir}/ $(TARGET_DIR); \
> - done
> + $(d)/ $(TARGET_DIR)$(sep))
>
> @$(foreach s, $(call qstrip,$(BR2_ROOTFS_POST_BUILD_SCRIPT)), \
> $(call MESSAGE,"Executing post-build script $(s)"); \
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-04-30 16:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 16:50 [Buildroot] [PATCH v2 0/3] Cleanup post-* loops Luca Ceresoli
2013-04-08 16:50 ` [Buildroot] [PATCH v2 1/3] post-build: show each script filename before execution Luca Ceresoli
2013-04-16 21:49 ` Yann E. MORIN
2013-04-17 16:13 ` Arnout Vandecappelle
2013-04-18 7:14 ` Yann E. MORIN
2013-04-24 20:15 ` Peter Korsgaard
2013-04-26 7:25 ` Luca Ceresoli
2013-04-30 16:57 ` Arnout Vandecappelle
2013-04-30 20:31 ` Peter Korsgaard
2013-04-08 16:50 ` [Buildroot] [PATCH v2 2/3] post-image: " Luca Ceresoli
2013-04-16 21:50 ` Yann E. MORIN
2013-04-24 20:16 ` Peter Korsgaard
2013-04-30 16:58 ` Arnout Vandecappelle
2013-04-08 16:50 ` [Buildroot] [PATCH v2 3/3] rootfs-overlay: use a make foreach instead of a shell for Luca Ceresoli
2013-04-16 21:55 ` Yann E. MORIN
2013-04-30 16:59 ` Arnout Vandecappelle [this message]
2013-04-30 20:33 ` Peter Korsgaard
2013-05-02 7:30 ` Luca Ceresoli
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=517FF854.9090903@mind.be \
--to=arnout@mind.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox