5b0c02a77a
BR2_DOWNLOAD_FORCE_CHECK_HASHES currently has the following dependency: depends on BR2_GLOBAL_PATCH_DIR != "" However, strictly speaking checking all hashes does not necessarily require using BR2_GLOBAL_PATCH_DIR, as long as you don't use custom versions. But more importantly: - Having this dependency means that this options is hidden when people don't use BR2_GLOBAL_PATCH_DIR. Instead the option should always be made visible, encouraging people to turn it on. - The Config.in comment was there to mitigate this previous argument, but this comment then shows up all the time when you have an empty global patch dir. This seems over-complicated, and it sounds much easier to have the option unconditionally available, and visible, and clarify in its help text that in order to this to work fully with custom package versions, BR2_GLOBAL_PATCH_DIR can be used to provide extra hash files. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> [yann.morin.1998@free.fr: - fix typo noticed by Peter K. - reword kast sentence after review by Peter K. ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> |
||
|---|---|---|
| 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