From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 1/2] Makefile: add target-genimage
Date: Mon, 16 Feb 2015 11:41:25 -0500 (EST) [thread overview]
Message-ID: <2004056362.2924318.1424104885214.JavaMail.root@savoirfairelinux.com> (raw)
In-Reply-To: <CANxTyt4ojT7Y+mG9+Je_gY0dD2Ub3nxfcuoXtD1F-sPcbcmY6g@mail.gmail.com>
Hi Danomi,
> A couple nitpicks ...
[...]
> > The rational behind adding this to Buildroot is that genimage
> > requires
>
> spelling: "rationale".
Thanks.
[...]
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -434,7 +434,7 @@ world: target-post-image
> >
> > .PHONY: all world toolchain dirs clean distclean source
> > outputmakefile \
> > legal-info legal-info-prepare legal-info-clean printvars \
> > - target-finalize target-post-image \
> > + target-finalize target-genimage target-post-image \
> > $(TARGETS) $(TARGETS_ROOTFS) \
> > $(TARGETS_DIRCLEAN) $(TARGETS_SOURCE) $(TARGETS_LEGAL_INFO)
> > \
> > $(BUILD_DIR) $(STAGING_DIR) $(TARGET_DIR) \
> > @@ -621,7 +621,20 @@ endif
> > $(call MESSAGE,"Executing post-build script $(s)");
> > \
> > $(EXTRA_ENV) $(s) $(TARGET_DIR) $(call
> > qstrip,$(BR2_ROOTFS_POST_SCRIPT_ARGS))$(sep))
> >
> > -target-post-image: $(TARGETS_ROOTFS) target-finalize
> > +target-genimage: $(TARGETS_ROOTFS) target-finalize
> > + @$(foreach cfg, $(call qstrip,$(BR2_ROOTFS_GENIMAGE_CFG)),
> > \
> > + $(call MESSAGE,"Executing genimage with config $(cfg)"); \
> > + T=$$(mktemp -d $(BUILD_DIR)/.genimage.XXXXXXXXXX); \
> > + mkdir -p $$T/{root,tmp}; \
> > + $(EXTRA_ENV) output/host/usr/bin/genimage \
> > + --rootpath $$T/root \
> > + --tmppath $$T/tmp \
> > + --inputpath output/images/ \
> > + --outputpath output/images/ \
> > + --config $(cfg); \
> > + rm -rf $$T$(sep))
>
> I don't think the final $(sep) is needed, since this the last line of
> a makefile target, as opposed to, say. a template.
Are you sure? I'm not sure either but I tried to follow the other foreach
statements.
Thanks for the nitpicks. Other than that, an feedback on the overall RFC?
Regards,
Vivien
next prev parent reply other threads:[~2015-02-16 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 22:33 [Buildroot] [RFC 0/2] add a minimal genimage support Vivien Didelot
2015-02-12 22:33 ` [Buildroot] [RFC 1/2] Makefile: add target-genimage Vivien Didelot
2015-02-14 17:24 ` Danomi Manchego
2015-02-16 16:41 ` Vivien Didelot [this message]
2015-02-17 2:37 ` Danomi Manchego
2015-02-25 10:48 ` Zoltan Gyarmati
2015-02-12 22:33 ` [Buildroot] [RFC 2/2] boards/raspberrypi: add a sample genimage config Vivien Didelot
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=2004056362.2924318.1424104885214.JavaMail.root@savoirfairelinux.com \
--to=vivien.didelot@savoirfairelinux.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.