b89648b4d0
When selecting barebox in menuconfig, BR2_TARGET_BAREBOX_IMAGE_FILE will be empty by default, which causes Buildroot to install whatever the barebox-flash-image symlink points at for barebox versions >= v2012.10.0. This is an outdated fallback, because barebox-flash-image is only valid when the barebox build produces a single binary. Virtually all new defconfigs added in the last couple of years are multiconfig (CONFIG_PBL_IMAGE=y) however, meaning that a single imx_v7_defconfig or multi_v8_defconfig will produce many images that support different boards or even platforms. As there is no single valid target for barebox-flash-image to point at in this case, this symlink will point at a non-existing 'multi-image-build' to alert the user to this fact. As replacement for barebox-flash-image, barebox commit 550cf79c216a ("Make list of flash images and fix link all single image cases") first released with v2015.12.0 creates a barebox-flash-images file with a list of all images built by barebox. Have buildroot use that file as a fallback before trying barebox-flash-image to have a fallback that works for any recent barebox defconfig as well. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> |
||
---|---|---|
arch | ||
board | ||
boot | ||
configs | ||
docs | ||
fs | ||
linux | ||
package | ||
support | ||
system | ||
toolchain | ||
utils | ||
.checkpackageignore | ||
.clang-format | ||
.defconfig | ||
.editorconfig | ||
.flake8 | ||
.gitignore | ||
.gitlab-ci.yml | ||
.shellcheckrc | ||
CHANGES | ||
Config.in | ||
Config.in.legacy | ||
COPYING | ||
DEVELOPERS | ||
Makefile | ||
Makefile.legacy | ||
README |
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on OFTC IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches