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
- Acquiring Buildroot
- Build system prerequisites
- Cross-compiler terminology: build, host, target, sysroot
- Selecting the appropriate target
- Constructing a minimal embedded system and booting it
- Inspection of the resulting filesystem image contents
- Parallel builds
- Full and partial rebuilds
- Design Goals of Buildroot
- Key Decisions
- C library selection: glibc, uClibc, or musl?
- Init system choice: busybox versus sysVinit versus systemd
- Management of device nodes in /dev
- Selection of other packages
- Understanding Build Instructions
- Syntax of Kconfig (Config.in) files
- GNU Make features employed in Buildroot Makefiles
- Style guide for Config.in and *.mk files
- Incorporating a simple Autotools-based package
- Distinction between staging and target directories
- The necessity of host packages
- Expressing dependencies and optional features
- Support for languages other than C and build systems beyond Autotools
- Debugging Makefiles
- Rebuilding a single package
- Analyzing Build Results
- Identifying what caused prolonged build times?
- Understanding what consumed significant disk space?
- Determining 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
- Reviewing build logs
- Addressing Common Cross-Compilation Challenges
- 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 start at boot
- Supplying custom configuration files
- Available firmware update mechanisms
- Upgrading to a newer Buildroot version
- Ensuring compliance with open-source licenses
Requirements
- Participants must have built a kernel at least once for a standard desktop (non-embedded) Linux system.
- Understanding of the components that make up the Linux userspace on a desktop environment.
- Ability to generate and apply patches.
- Capability to explain GNU Make, Autotools, and identify other existing build systems.
- Preferably, experience maintaining at least one Linux package, either as an upstream author or within a traditional Linux desktop distribution.
- Previous experience with embedded development is not required and cannot substitute for the desktop Linux knowledge outlined above.
7 Hours
