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 correct 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 be made
- C library: glibc, uClibc, or musl?
- Init system: BusyBox, SysVinit, or systemd?
- Managing device nodes in /dev
- Selecting additional packages
- Understanding build instructions
- Syntax of Kconfig (Config.in) files
- GNU Make features used by Buildroot Makefiles
- Style guide for Config.in and *.mk files
- How to add a simple Autotools-based package
- Differences between staging and target directories
- The need for 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
- Analysing build results
- What consumed the most build time?
- What occupied the most disk space?
- Why was this package built?
- Organising external package trees
- Workflow for application developers
- Using a local source directory
- Overriding build instructions
- Debugging your application
- Accelerating rebuilds
- Reviewing build logs
- Addressing common cross-compilation issues
- Writing cross-compiler-friendly software
- Workflow for kernel developers
- How the kernel boots on an embedded system
- Modifying configuration options and applying patches
- Module loading mechanisms
- Preparing 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 licences
Requirements
- Participants must have previously built a kernel at least once for a traditional desktop (non-embedded) Linux system.
- Understand the components that make up the Linux userspace on a desktop system.
- Know how to generate and apply patches.
- Be able to explain the concepts of GNU Make, Autotools, and other build systems.
- Ideally, maintain at least one Linux package, either as an upstream author or within a traditional Linux desktop distribution.
- Prior experience with embedded development is not required, but it does not replace the knowledge of traditional Linux desktops outlined above.
7 Hours
