How cnlohr/buildroot works
Buildroot generates embedded Linux systems by configuring a target and package set, cross-compiling it, and producing images. The README documents this user workflow and the resulting kernel, bootloader, and root filesystem, but the supplied tree is a selected-file snapshot rather than the build-system implementation. The graph therefore uses documented edges for the main workflow and shows sampled Kconfig, toolchain, and image-utility components without assuming their unsampled call relationships. Package checks and test infrastructure are separate supporting branches.
Main entry points: qconf.cc Qt configuration · kconfig Kconfig engine · emulator.py QEMU emulator · zynqmp Board configurations
Components 16
Configuration
- Kconfig interfaces
support/kconfig - Qt configuration
support/kconfig/qconf.cc - Kconfig engine
support/kconfig - Board configurations
board/zynqmp
Cross-compilation
- Buildroot build
- Toolchain wrapper
toolchain/toolchain-wrapper.c - Package compilation
System outputs
- Kernel, bootloader, rootfs
- Device-node creation
package/makedevs/makedevs.c - Pimage utility
package/mkpimage/mkpimage.c
Checks and tests
- Package checks
utils/checkpackagelib - Symbol checks
utils/checksymbolslib - Test builder
support/testing/infra/builder.py - QEMU emulator
support/testing/infra/emulator.py
Other components
- Build user
- QEMU
Connections 15
- Build user → Kconfig interfaces: configures target
README - Build user → Qt configuration: configures target
README - Kconfig interfaces → Kconfig engine: sets configuration
- Qt configuration → Kconfig engine: sets configuration
support/kconfig/qconf.cc - Qt configuration → Kconfig engine: uses interfaces
support/kconfig/qconf.cc - Build user → Buildroot build: starts build
README - Buildroot build → Toolchain wrapper: cross-compiles
- Buildroot build → Package compilation: builds packages
README - Buildroot build → Kernel, bootloader, rootfs: produces images
README - Board configurations → Buildroot build: selects board
- Package compilation → Device-node creation: uses utility
- Package compilation → Pimage utility: uses utility
- Package checks → Symbol checks: checks separately
- Test builder → QEMU emulator: runs tests with
support/testing/infra/basetest.py - QEMU emulator → QEMU: starts
support/testing/infra/emulator.py