From 2b0f455254149bd0c41c463a58c00d218922f002 Mon Sep 17 00:00:00 2001 From: "Yann E. MORIN" Date: Sun, 13 Jan 2013 11:52:20 +0000 Subject: Makefile: export a few variables to help support scripts Support scripts (in support/) may need to parse the .config file, so give them an easy access to it, by exporting BUILDROOT_CONFIG with the fully- qualified path to .config. Also, post-build scripts may need to reference a few locations, so export those, too. Note: we export both O and BASE_DIR. Although they are the same, BASE_DIR is used internally, while O is used on the command line, which makes it a bit ambiguous to know which to use. As users use O= on the command line, they will probably tend to use that in their post-build scripts. Update doc accordingly. [Peter: fixed typo] Signed-off-by: "Yann E. MORIN" Cc: Arnout Vandecappelle Cc: Thomas Petazzoni cc: Peter Korsgaard Signed-off-by: Peter Korsgaard --- docs/manual/customize-rootfs.txt | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'docs/manual/customize-rootfs.txt') diff --git a/docs/manual/customize-rootfs.txt b/docs/manual/customize-rootfs.txt index a1a556b85..4d3b55970 100644 --- a/docs/manual/customize-rootfs.txt +++ b/docs/manual/customize-rootfs.txt @@ -37,6 +37,13 @@ there are a few ways to customize the resulting target filesystem. certain package generates wrong or unneeded files, you should fix that package rather than work around it with a post-build cleanup script. _Among these first 3 methods, this one should be preferred_. + You may also use these variables in your post-build script: + - +BUILDROOT_CONFIG+: the path to the Buildroot .config file + - +HOST_DIR+, +STAGING_DIR+, +TARGET_DIR+: see + xref:generic-package-reference[] + - +BINARIES_DIR+: the place where all binary files (aka images) are + stored + - +BASE_DIR+ (or +O+): the base output directory * A special package, 'customize', stored in +package/customize+ can be used. You can put all the files that you want to see in the final -- cgit v1.2.3