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
- Constructing a minimal embedded system and booting it
- Contents of the resulting filesystem image
- Parallel builds
- Full and partial rebuilds
- Design goals of Buildroot
- Key Decisions
- Choosing a C library: glibc, uClibc, or musl?
- Choosing an init system: busybox vs sysVinit vs systemd
- Managing device nodes in /dev
- Selecting other packages
- Understanding Build Instructions
- Syntax of Kconfig (Config.in) files
- GNU Make features utilized in Buildroot Makefiles
- Style guide for Config.in and *.mk files
- Incorporating a simple Autotools-based package
- Difference between staging and target directories
- The necessity of host packages
- Defining 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 what consumed significant build time
- Identifying what consumed significant disk space
- Understanding why a specific package was built
- Organizing external package trees
- Workflow for Application Developers
- Utilizing 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 how the kernel boots on an embedded system
- Modifying configuration options and adding patches
- Module loading mechanisms
- Creating a Finished Product
- Running daemons at startup
- Providing custom configuration files
- Available 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 create and apply patches.
- Knowledge of GNU Make, Autotools, and other existing build systems.
- Experience maintaining at least one Linux package, either as an upstream author or within a traditional Linux desktop distribution, is ideal.
- Prior embedded development experience is not required and cannot substitute for the knowledge of traditional Linux desktops outlined above.
7 Hours
