mirror of
https://github.com/godotengine/buildroot.git
synced 2026-01-08 02:09:48 +03:00
c3493069f2
Since forever, we run 'menuconfig' automatically on an unconfigured tree. However, this does not help users that much: - If they read the documentation, they should already know to run make menuconfig first. - If they haven't read the documentation, dropping them in menuconfig isn't very helpful. - It's a likely that the user didn't intend to be in an unconfigured tree (e.g. wrong O= specified), so starting menuconfig (and polluting this wrong O= directory) is not very helpful. - It's possible that the user really doesn't want menuconfig, but instead needs xconfig, or some defconfig, or ... So, instead of trying to guess what the user needs, print an error and let the user decide what to do next. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
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 Freenode IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches