From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] Makefile.package.in: Makes it possible to override the default extract commands
Date: Tue, 10 May 2011 09:16:59 +0200 [thread overview]
Message-ID: <20110510091659.5274152c@surf> (raw)
In-Reply-To: <1305008226-8906-2-git-send-email-a@awn.dk>
Hello Allan,
On Tue, 10 May 2011 08:17:04 +0200
"Allan W. Nielsen" <a@awn.dk> wrote:
> When using GENTARGETS (or macroes depending on it), there is no way of
> specifying a custom extraction procedure. When using the patch one can
> simply define $(PACKAGE_NAME)_EXTRACT_CMDS which will override the
> default. If non is defined it will fall back to the default extract
> procedure.
I like the feature added by this patch (it is needed for strange
packages), but I'm not sure about the implementation.
> -# Unpack the archive
> +# Unpack the archive using custom commands
> +$(BUILD_DIR)/%/.stamp_custom_extracted:
> + @$(call MESSAGE,"Extracting - custom")
> + $(Q)mkdir -p $(@D)
> + $($(PKG)_EXTRACT_CMDS)
> + $(foreach hook,$($(PKG)_POST_EXTRACT_HOOKS),$(call $(hook))$(sep))
> + $(Q)touch $@
> +
> +# Unpack the archive using default commands
> $(BUILD_DIR)/%/.stamp_extracted:
> - @$(call MESSAGE,"Extracting")
> + @$(call MESSAGE,"Extracting - default")
> $(Q)mkdir -p $(@D)
> $(Q)$(if $($(PKG)_SOURCE),$(INFLATE$(suffix $($(PKG)_SOURCE))) $(DL_DIR)/$($(PKG)_SOURCE) | \
> $(TAR) $(TAR_STRIP_COMPONENTS)=1 -C $(@D) $(TAR_OPTIONS) -)
Instead of having two different stamp files, isn't possible to define
the extract step as follows :
> +$(BUILD_DIR)/%/.stamp_extracted:
> + @$(call MESSAGE,"Extracting")
> + $(Q)mkdir -p $(@D)
> + $($(PKG)_EXTRACT_CMDS)
> + $(foreach hook,$($(PKG)_POST_EXTRACT_HOOKS),$(call $(hook))$(sep))
> + $(Q)touch $@
And then have the $(PKG)_EXTRACT_CMDS variable be define to the default
value, unless it has already been defined ?
Note that I haven't looked closely whether it was possible or not. But
if it is, then I would prefer such an implementation.
Thanks for doing this work!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-05-10 7:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 6:17 [Buildroot] Minor updates to Makefile.package.in Allan W. Nielsen
2011-05-10 6:17 ` [Buildroot] [PATCH 1/3] Makefile.package.in: Makes it possible to override the default extract commands Allan W. Nielsen
2011-05-10 7:08 ` Daniel Nyström
2011-05-10 7:16 ` Thomas Petazzoni [this message]
[not found] ` <BANLkTi=HirqhyL4uuuBWnUoKu36xGE+V2g@mail.gmail.com>
2011-05-10 9:03 ` Thomas Petazzoni
2011-05-10 6:17 ` [Buildroot] [PATCH 2/3] Makefile.package.in: Added LZMA as compression type Allan W. Nielsen
2011-05-10 6:52 ` Thomas Petazzoni
2011-07-12 21:15 ` Peter Korsgaard
2011-05-10 6:17 ` [Buildroot] [PATCH 3/3] Makefile.package.in: Fixing git download method Allan W. Nielsen
2011-05-10 6:53 ` Thomas Petazzoni
[not found] ` <BANLkTinQcHkTmHoq9ci_QYgaj8vAqZ07yQ@mail.gmail.com>
2011-05-10 7:36 ` 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=20110510091659.5274152c@surf \
--to=thomas.petazzoni@free-electrons.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