From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Packages Post-extract pre-patch phase ?
Date: Sun, 5 Jun 2011 21:23:50 +0200 [thread overview]
Message-ID: <20110605212350.17cff2fd@skate> (raw)
In-Reply-To: <1307284805.2767.10.camel@ceri>
Le Sun, 05 Jun 2011 15:40:05 +0100,
Mike Davies <busybox_mail@rovoreed.com> a ?crit :
> Is it possible to have a "post extract" or "pre patch" phase ?
Yes, you have the <pkg>_POST_EXTRACT_HOOKS variable for each package,
which can contain a list of make macros to call after the package
extraction.
See package/dropbear/dropbear.mk for an example.
The documentation should be updated to reflect the availability of this
hook point. Would you volunteer to send a patch to update the
documentation ?
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-06-05 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 14:40 [Buildroot] Packages Post-extract pre-patch phase ? Mike Davies
2011-06-05 19:23 ` Thomas Petazzoni [this message]
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=20110605212350.17cff2fd@skate \
--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