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.
+
+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
+ BR2_EXTERNAL, TOPDIR etc. to refer to the custom
+ environment.
+
+ 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.
$(1)_LICENSE = GPLv2 with exceptions
$(1)_LICENSE_FILES = COPYING
+$(1)_CUSTOM_EMBEDDED_ENV_PATH = $$(call qstrip,$$(BR2_TARGET_$(1)_CUSTOM_EMBEDDED_ENV_PATH))
+
ifneq ($$(call qstrip,$$(BR2_TARGET_BAREBOX_CUSTOM_PATCH_DIR)),)
define $(1)_APPLY_CUSTOM_PATCHES
$$(APPLY_PATCHES) $$(@D) \
endef
endif
+ifneq ($$($(1)_CUSTOM_EMBEDDED_ENV_PATH),)
+define $(1)_KCONFIG_FIXUP_CMDS
+ $$(call KCONFIG_ENABLE_OPT,CONFIG_DEFAULT_ENVIRONMENT,$$(@D)/.config)
+ $$(call KCONFIG_SET_OPT,CONFIG_DEFAULT_ENVIRONMENT_PATH,"$$($(1)_CUSTOM_EMBEDDED_ENV_PATH)",$$(@D)/.config)
+endef
+endif
+
define $(1)_BUILD_CMDS
$$($(1)_BUILD_BAREBOXENV_CMDS)
$$(TARGET_MAKE_ENV) $$(MAKE) $$($(1)_MAKE_FLAGS) -C $$(@D)
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.
+
+config BR2_TARGET_BAREBOX_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
+ BR2_EXTERNAL, TOPDIR etc. to refer to the custom
+ environment.
+
+ 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.