The Buildroot User Manual
User Manual: Pdf
Open the PDF directly: View PDF
Page Count: 117 [warning: Documents this large are best viewed by clicking the View PDF Link!]
- I Getting started
- II User guide
- Buildroot configuration
- Configuration of other components
- General Buildroot usage
- make tips
- Understanding when a full rebuild is necessary
- Understanding how to rebuild packages
- Offline builds
- Building out-of-tree
- Environment variables
- Dealing efficiently with filesystem images
- Graphing the dependencies between packages
- Graphing the build duration
- Graphing the filesystem size contribution of packages
- Integration with Eclipse
- Advanced usage
- Project-specific customization
- Recommended directory structure
- Keeping customizations outside of Buildroot
- Storing the Buildroot configuration
- Storing the configuration of other components
- Customizing the generated target filesystem
- Adding custom user accounts
- Customization after the images have been created
- Adding project-specific patches
- Adding project-specific packages
- Quick guide to storing your project-specific customizations
- Frequently Asked Questions & Troubleshooting
- The boot hangs after Starting network…
- Why is there no compiler on the target?
- Why are there no development files on the target?
- Why is there no documentation on the target?
- Why are some packages not visible in the Buildroot config menu?
- Why not use the target directory as a chroot directory?
- Why doesn't Buildroot generate binary packages (.deb, .ipkg…)?
- How to speed-up the build process?
- Known issues
- Legal notice and licensing
- Beyond Buildroot
- III Developer guide
- How Buildroot works
- Coding style
- Adding support for a particular board
- Adding new packages to Buildroot
- Package directory
- Config files
- The .mk file
- The .hash file
- Infrastructure for packages with specific build systems
- Infrastructure for autotools-based packages
- Infrastructure for CMake-based packages
- Infrastructure for Python packages
- Infrastructure for LuaRocks-based packages
- Infrastructure for Perl/CPAN packages
- Infrastructure for virtual packages
- Infrastructure for packages using kconfig for configuration files
- Infrastructure for rebar-based packages
- Infrastructure for Waf-based packages
- Infrastructure for packages building kernel modules
- Infrastructure for asciidoc documents
- Infrastructure specific to the Linux kernel package
- Hooks available in the various build steps
- Gettext integration and interaction with packages
- Tips and tricks
- Conclusion
- Patching a package
- Download infrastructure
- Debugging Buildroot
- Contributing to Buildroot
- DEVELOPERS file and get-developers
- IV Appendix