Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
Course Outline
- Getting Started
- Obtaining Buildroot
- Build system requirements
- Cross-compiler terminology: build, host, target, sysroot
- Selecting the appropriate target
- Building and booting a minimal embedded system
- Contents of the resulting filesystem image
- Parallel builds
- Full and partial rebuilds
- Design Goals of Buildroot
- Key Decisions to Make
- C library: glibc, uClibc, or musl?
- Init system: busybox versus sysVinit versus systemd
- Managing device nodes in /dev
- Selecting additional packages
- Understanding Build Instructions
- Kconfig (Config.in) file syntax
- GNU Make features utilized by Buildroot Makefiles
- Style guide for Config.in and *.mk files
- Adding a simple Autotools-based package
- Differences between staging and target directories
- The necessity of host packages
- Expressing dependencies and optional features
- Support for languages other than C and build systems other than Autotools
- Debugging Makefiles
- Rebuilding a single package
- Analyzing Build Results
- Identifying time-consuming build steps
- Identifying disk space usage
- Understanding why specific packages were built
- Organizing External Package Trees
- Workflow for Application Developers
- Using a local source directory
- Overriding build instructions
- Debugging your application
- Accelerating rebuilds
- Viewing build logs
- Addressing Common Cross-Compilation Issues
- Writing software that is compatible with cross-compilers
- Workflow for Kernel Developers
- Understanding kernel boot processes on embedded systems
- Modifying configuration options and applying patches
- Module loading mechanisms
- Finalizing the Product
- Configuring daemons to run at startup
- Providing custom configuration files
- Firmware update mechanisms
- Upgrading to a new Buildroot version
- Complying with open-source licenses
Requirements
- Participants must have compiled a kernel at least once for a traditional desktop (non-embedded) Linux system.
- Understanding of the components that make up the Linux userspace on a desktop system.
- Ability to generate and apply patches.
- Knowledge of GNU Make and Autotools, as well as familiarity with other build systems.
- Preferably, experience maintaining at least one Linux package, either as an upstream author or within a traditional Linux desktop distribution.
- Previous embedded development experience is not required and does not substitute for the knowledge of traditional Linux desktops outlined above.
7 Hours
