NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Makefile: export a few variables to help support scripts

Browse Source 
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" <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
cc: Peter Korsgaard <jacmet@uclibc.org>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
This commit is contained in:
Yann E. MORIN 2013-01-13 11:52:20 +00:00 committed by Peter Korsgaard
parent 766862434b
commit 2b0f455254
2 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Makefile
View File

@ -91,6 +91,8 @@ EXTRAMAKEARGS = O=$(O)
NEED_WRAPPER=y
endif
BUILDROOT_CONFIG=$(CONFIG_DIR)/.config
# Pull in the user's configuration file
ifeq ($(filter $(noconfig_targets),$(MAKECMDGOALS)),)
-include $(CONFIG_DIR)/.config
@ -282,6 +284,15 @@ HOSTCC := $(CCACHE) $(HOSTCC)
HOSTCXX := $(CCACHE) $(HOSTCXX)
endif
# Scripts in support/ or post-build scripts may need to reference
# these locations, so export them so it is easier to use
export BUILDROOT_CONFIG
export TARGET_DIR
export STAGING_DIR
export HOST_DIR
export BINARIES_DIR
export BASE_DIR O # O and BASE_DIR are the same
#############################################################
#
# You should probably leave this stuff alone unless you know

7
docs/manual/customize-rootfs.txt
View File

@ -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