aa87875b9f
The licensing terms are inherited from the target variant to the host variant: when the host _LICENSE is empty, then the value of the target _LICENSE is used. However, for the golang infra, we want to append a little blurb about vendored depndencies. If the package is a host-only, then it would inherit the target _LICENSE, i.e. the variable without the leading HOST_. If that is defined, this is inherited in the generic-package part of the infra, but in the golang infra, we saw an empty variable, and so we would not add the vendoring blurb. We can't move the condition appending that blurb, after we called into the generic-package infra, otherwise in that case, we'd have the opposite issue for packages that are both target and host packages, where the blurb would be duplicated for host packages... Instead, we workaround the issue by duplicating the heuristic to inherit the target value, from the generic- into the golang-package infra. Signed-off-by: Yann E. MORIN <yann.morin@orange.com> Signed-off-by: Arnout Vandecappelle <arnout@mind.be> |
||
|---|---|---|
| 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