Like all good problems, disparate pieces work together to create a "synergistically" hairy mess. The sortGrid() overhaul highlighted a flaw in pkg-stats allowing for duplicate package class names across rows. As an example, boot/barebox/barebox.mk and boot/barebox/barebox/barebox.mk both get the classname ._barebox and so sortGrid() sticks them on the same line giving a table with a vestigal row sticking out of the right side like some kind of appendage. Also I neglected to add a "_" to the current version column's cells pkgname class so instead of "._pkgname" we had ".pkgname" and so the cells were not collected properly as part of the row. These issues explain the formatting weirdness. package classnames are now ".path_to_package_makefile" without suffix (.mk) (so ._boot_barebox_barebox and ._boot_barebox_barebox_barebox instead of ._barebox) in order to guarantee uniqueness. and what was *accidentally* class="centered current_version data .barebox" is now class="centered current_version data ._boot_barebox_barebox" just like *all* the other cells in the row. :p Signed-off-by: Sen Hastings <sen@phobosdpl.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> |
||
---|---|---|
arch | ||
board | ||
boot | ||
configs | ||
docs | ||
fs | ||
linux | ||
package | ||
support | ||
system | ||
toolchain | ||
utils | ||
.clang-format | ||
.defconfig | ||
.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