From: "Émeric Vigier" <emeric.vigier@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-infra: limit -reconfigure and -rebuild actions
Date: Fri, 20 Jul 2012 11:34:44 -0400 (EDT) [thread overview]
Message-ID: <2133019142.1267214.1342798484932.JavaMail.root@mail.savoirfairelinux.com> (raw)
In-Reply-To: <1342791572-18657-1-git-send-email-rbraun@sceen.net>
Thanks for coming up with a patch following yesterday discussion. Got some comments though:
----- Mail original -----
> The -reconfigure and -rebuild per package targets unconditionally
> recreate the root filesystem image by depending on the all target.
> Restrict their actions to their package instead.
>
> Signed-off-by: Richard Braun <rbraun@sceen.net>
> ---
> package/pkg-generic.mk | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/pkg-generic.mk b/package/pkg-generic.mk
> index c01440e..f5b05a3 100644
> --- a/package/pkg-generic.mk
> +++ b/package/pkg-generic.mk
> @@ -389,12 +389,12 @@ endif
> rm -f $$($(2)_TARGET_INSTALL_IMAGES)
> rm -f $$($(2)_TARGET_INSTALL_HOST)
>
> -$(1)-rebuild: $(1)-clean-for-rebuild all
> +$(1)-rebuild: $(1)-clean-for-rebuild $(1)
>
> $(1)-clean-for-reconfigure: $(1)-clean-for-rebuild
> rm -f $$($(2)_TARGET_CONFIGURE)
>
> -$(1)-reconfigure: $(1)-clean-for-reconfigure all
> +$(1)-reconfigure: $(1)-clean-for-reconfigure $(1)-configure
Your patch makes -reconfigure clean-for-rebuild and then (just) -configure, without rebuilding.
That's ok to me, but you have to choose between:
1. updating docs/manual/rebuilding-packages.txt accordingly, especially:
"For convenience, most packages support the special make targets
<package>-reconfigure and <package>-rebuild to repeat the configure
and build steps"
2. or keep -reconfigure rebuilding the entire package, i.e.:
-+$(1)-reconfigure: $(1)-clean-for-reconfigure $(1)-configure
++$(1)-reconfigure: $(1)-clean-for-reconfigure $(1)
>
> # define the PKG variable for all targets, containing the
> # uppercase package variable prefix
> --
> 1.7.2.5
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Emeric
next prev parent reply other threads:[~2012-07-20 15:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 13:39 [Buildroot] [PATCH] pkg-infra: limit -reconfigure and -rebuild actions Richard Braun
2012-07-20 15:34 ` Émeric Vigier [this message]
2012-07-20 15:58 ` Richard Braun
2012-07-20 21:55 ` Émeric Vigier
2012-07-20 20:27 ` Thomas Petazzoni
2012-07-20 23:31 ` Richard Braun
2012-07-21 12:54 ` Thomas Petazzoni
2012-07-21 15:17 ` Richard Braun
2012-07-21 16:14 ` Samuel Martin
2012-07-22 18:27 ` Alex Bradbury
2012-12-14 13:49 ` Arnout Vandecappelle
2012-07-24 23:07 ` Arnout Vandecappelle
2012-08-02 13:28 ` Alex Bradbury
2012-08-02 13:36 ` Thomas Petazzoni
2012-09-21 16:57 ` Alex Bradbury
2012-07-22 19:20 ` Stephan Hoffmann
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=2133019142.1267214.1342798484932.JavaMail.root@mail.savoirfairelinux.com \
--to=emeric.vigier@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox