2522fa8ed7
Allow user to supply their own step-hooks by passing a variable
on the make command-line:
make BR2_INSTRUMENTATION_SCRIPTS=/path/to/my/script
This can be useful to run site-specific actions at each step of the
build process, such as logging installed, removed or modified files,
do sanity checks on installed files...
It is possible to call more than one script, by passing a space-separated
lists of scripts to call.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>
Reviewed-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Reviewed-by: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
34 lines
1.1 KiB
Plaintext
34 lines
1.1 KiB
Plaintext
// -*- mode:doc; -*-
|
|
// vim: set syntax=asciidoc:
|
|
|
|
[[debugging-buildroot]]
|
|
|
|
Debugging Buildroot
|
|
-------------------
|
|
|
|
It is possible to instrument the steps +Buildroot+ does when building
|
|
packages. Define the variable +BR2_INSTRUMENTATION_SCRIPTS+ to contain
|
|
the path of one or more scripts (or other executables), in a
|
|
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
|
|
|
|
For example :
|
|
|
|
----
|
|
make BR2_INSTRUMENTATION_SCRIPTS="/path/to/my/script1 /path/to/my/script2"
|
|
----
|
|
|
|
That script has access to the following variables:
|
|
|
|
- +BUILDROOT_CONFIG+: the path to the Buildroot .config file
|
|
- +HOST_DIR+, +STAGING_DIR+, +TARGET_DIR+: see
|
|
xref:generic-package-reference[]
|
|
- +BUILD_DIR+: the directory where packages are extracted and built
|
|
- +BINARIES_DIR+: the place where all binary files (aka images) are
|
|
stored
|
|
- +BASE_DIR+: the base output directory
|