2016-04-24 23:15:24 +02:00
|
|
|
choice
|
|
|
|
|
prompt "Barebox configuration"
|
|
|
|
|
default BR2_TARGET_BAREBOX_AUX_USE_DEFCONFIG
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_BAREBOX_AUX_USE_DEFCONFIG
|
|
|
|
|
bool "Using a defconfig"
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_BAREBOX_AUX_USE_CUSTOM_CONFIG
|
|
|
|
|
bool "Using a custom config file"
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_BAREBOX_AUX_BOARD_DEFCONFIG
|
|
|
|
|
string "board defconfig"
|
|
|
|
|
depends on BR2_TARGET_BAREBOX_AUX_USE_DEFCONFIG
|
|
|
|
|
help
|
|
|
|
|
Name of the board for which Barebox should be built, without
|
|
|
|
|
the _defconfig suffix.
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_BAREBOX_AUX_CUSTOM_CONFIG_FILE
|
|
|
|
|
string "Configuration file path"
|
|
|
|
|
depends on BR2_TARGET_BAREBOX_AUX_USE_CUSTOM_CONFIG
|
|
|
|
|
help
|
|
|
|
|
Path to the barebox configuration file
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_BAREBOX_AUX_CONFIG_FRAGMENT_FILES
|
|
|
|
|
string "Additional configuration fragment files"
|
|
|
|
|
help
|
|
|
|
|
A space-separated list of configuration fragment files,
|
|
|
|
|
that will be merged to the main Barebox configuration file.
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_BAREBOX_AUX_IMAGE_FILE
|
|
|
|
|
string "Image filename"
|
|
|
|
|
help
|
|
|
|
|
Name of the generated barebox image, which will be copied to
|
|
|
|
|
the images directory.
|
|
|
|
|
|
|
|
|
|
If left empty, defaults to:
|
|
|
|
|
- barebox.bin for barebox versions older than 2012.10.
|
|
|
|
|
- barebox-flash-image for later versions.
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_BAREBOX_AUX_CUSTOM_ENV
|
|
|
|
|
bool "Generate an environment image"
|
|
|
|
|
help
|
|
|
|
|
Generate a custom environment image. This environment will
|
|
|
|
|
contain the variables and scripts to be used at boot by
|
|
|
|
|
barebox.
|
|
|
|
|
|
|
|
|
|
config BR2_TARGET_BAREBOX_AUX_CUSTOM_ENV_PATH
|
|
|
|
|
string "Environment path"
|
|
|
|
|
depends on BR2_TARGET_BAREBOX_AUX_CUSTOM_ENV
|
|
|
|
|
help
|
|
|
|
|
Path to the directory containing the custom barebox
|
|
|
|
|
environment. Depending on your setup, it will probably be
|
|
|
|
|
based on either the content of the defaultenv or
|
|
|
|
|
defaultenv-2 directories in the barebox source code, plus
|
|
|
|
|
the additions needed. The output will be an image in the
|
|
|
|
|
barebox devfs format, stored in the images directory, with
|
|
|
|
|
the same name as the directory name given here.
|
2016-05-06 07:46:04 +02:00
|
|
|
|
|
|
|
|
config BR2_TARGET_BAREBOX_AUX_CUSTOM_EMBEDDED_ENV_PATH
|
|
|
|
|
string "Embedded environment path"
|
|
|
|
|
help
|
|
|
|
|
If this option is not empty, it is the path to a custom
|
|
|
|
|
embedded barebox environment. This image will be used when
|
|
|
|
|
the environment found in the environment sector is
|
|
|
|
|
invalid. This option sets the barebox Kconfig option
|
|
|
|
|
CONFIG_DEFAULT_ENVIRONMENT_PATH to the specified path. This
|
|
|
|
|
way it is possible to use Buildroot variables like
|
core: introduce per br2-external NAME
This unique NAME is used to construct a per br2-external tree variable,
BR2_EXTERNAL_$(NAME)_PATH, which contains the path to the br2-external
tree.
This variable is available both from Kconfig (set in the Kconfig
snippet) and from the .mk files.
Also, display the NAME and its path as a comment in the menuconfig.
This will ultimately allow us to support multiple br2-external trees at
once, with that NAME (and thus BR2_EXTERNAL_$(NAME)) uniquely defining
which br2-external tree is being used.
The obvious outcome is that BR2_EXTERNAL should now no longer be used to
refer to the files in the br2-external tree; that location is now known
from the BR2_EXTERNAL_$(NAME)_PATH variable instead. This means we no
longer need to expose, and must stop from from exposing BR2_EXTERNAL as
a Kconfig variable.
Finally, this also fixes a latent bug in the pkg-generic infra, where we
would so far always refer to BR2_EXTERNAL (even if not set) to filter
the names of packages (to decide whether they are a bootloader, a
toolchain or a simple package).
Note: since the variables in the Makefile and in Kconfig are named the
same, the one we computed early on in the Makefile will be overridden by
the one in .config when we have it. Thus, even though they are set to
the same raw value, the one from .config is quoted and, being included
later in the Makefile, will take precedence, so we just re-include the
generated Makefile fragment a third time before includeing the
br2-external's Makefiles. That's unfortunate, but there is no easy way
around that as we do want the two variables to be named the same in
Makefile and Kconfig (and we can't ask the user to un-quote that variable
himself either), hence this little dirty triple-inclusion trick.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@openwide.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-14 16:39:17 +02:00
|
|
|
TOPDIR etc. to refer to the custom environment.
|
2016-05-06 07:46:04 +02:00
|
|
|
|
|
|
|
|
Depending on your setup, the custom embedded environment
|
|
|
|
|
will probably be based on either the content of the
|
|
|
|
|
defaultenv or defaultenv-2 directories in the barebox source
|
|
|
|
|
code.
|
