summaryrefslogtreecommitdiffstats
path: root/docs/manual/debugging-buildroot.txt
blob: b97f633bef4012bf1404297f810ef5bb587d3323 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
// -*- 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:

  - +BR2_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
OpenPOWER on IntegriCloud