mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-08-01 13:18:36 -09:00
85736a27c8
It is perfectly valid for a patch file to have trailing spaces, when for example an empty or space-only line is appears in a hunk: if the line if part of the context, whether it be empty or with only spaces, there will aways be the leading space introduced by the patch itsef, making for a sapce-only line; if the line is space-only and removed (or added) that will also appear as a space-only line. Currently, our editorconfig wants to unconditionally drop trailing spaces, so when one edits a patch file to add their SoB and Upstream tags, such a patch would get badly mangled and would not apply, causing quite some grief and questioning (sad experience looming in the recent past here)... Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
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