From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] docs/manual: add list of instrumentation steps
Date: Sun, 03 May 2015 18:28:59 +0200 [thread overview]
Message-ID: <55464CCB.9000201@mind.be> (raw)
In-Reply-To: <1430667764-17877-1-git-send-email-yann.morin.1998@free.fr>
On 03/05/15 17:42, Yann E. MORIN wrote:
> The names of steps are not obvious, so add this list to the manual.
>
> Small formatting fix at the same time.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Arnout Vandecappelle <arnout@mind.be>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Regards,
Arnout
>
> ---
> Changes v2 -> v3:
> - typoes (Arnout)
>
> Changes v1 -> v2:
> - remove reference to target-finalize, it's currently not a step
> ---
> docs/manual/debugging-buildroot.txt | 17 ++++++++++++++---
> 1 file changed, 14 insertions(+), 3 deletions(-)
>
> diff --git a/docs/manual/debugging-buildroot.txt b/docs/manual/debugging-buildroot.txt
> index b97f633..f575fc4 100644
> --- a/docs/manual/debugging-buildroot.txt
> +++ b/docs/manual/debugging-buildroot.txt
> @@ -12,8 +12,8 @@ space-separated list, you want called before and after each step. The
> scripts are called in sequence, with three parameters:
>
> - +start+ or +end+ to denote the start (resp. the end) of a step;
> - - the name of the step about to be started, or which just ended.
> - - the name of the package
> + - the name of the step about to be started, or which just ended;
> + - the name of the package.
>
> For example :
>
> @@ -21,7 +21,18 @@ For example :
> make BR2_INSTRUMENTATION_SCRIPTS="/path/to/my/script1 /path/to/my/script2"
> ----
>
> -That script has access to the following variables:
> +The list of steps is:
> +
> + - +extract+
> + - +patch+
> + - +configure+
> + - +build+
> + - +install-host+, when a host-package is installed in +$(HOST_DIR)+
> + - +install-target+, when a target-package is installed in +$(TARGET_DIR)+
> + - +install-staging+, when a target-package is installed in +$(STAGING_DIR)+
> + - +install-image+, when a target-package installs files in +$(BINARIES_DIR)+
> +
> +The script has access to the following variables:
>
> - +BR2_CONFIG+: the path to the Buildroot .config file
> - +HOST_DIR+, +STAGING_DIR+, +TARGET_DIR+: see
>
--
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:[~2015-05-03 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 15:42 [Buildroot] [PATCHv3] docs/manual: add list of instrumentation steps Yann E. MORIN
2015-05-03 16:28 ` Arnout Vandecappelle [this message]
2015-05-05 20:47 ` 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=55464CCB.9000201@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 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.