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 for government use
- Build System Requirements for government applications
- Cross-Compiler Terminology: Build, Host, Target, Sysroot
- Selecting the Appropriate Target for government systems
- Building and Booting a Minimal Embedded System for government operations
- Contents of the Resulting Filesystem Image for government deployments
- Parallel Builds for government efficiency
- Full and Partial Rebuilds for government projects
- Design Goals of Buildroot for government use
- Choices to Be Made
- C Library: glibc, uClibc, or musl for government systems?
- Init System: BusyBox vs. SysVinit vs. Systemd for government operations
- Managing Device Nodes in /dev for government applications
- Selecting Other Packages for government use
- Understanding the Build Instructions
- Syntax of Kconfig (Config.in) Files for government projects
- Features of GNU Make Used by Buildroot Makefiles for government systems
- Style Guide for Config.in and *.mk Files for government use
- How to Add a Simple Autotools-Based Package for government applications
- The Difference Between Staging and Target Directories for government builds
- The Need for Host Packages in government projects
- Expressing Dependencies and Optional Features for government systems
- Support for Languages Other Than C and Build Systems Other Than Autotools for government use
- Debugging Makefiles for government operations
- Rebuilding a Single Package for government efficiency
- Analyzing the Build Results
- What Consumed So Much Build Time for government systems?
- What Consumed So Much Disk Space for government projects?
- Why Was This Package Built for government operations?
- Organizing External Package Trees for government use
- Workflow for Application Developers
- How to Use a Local Source Directory for government applications
- Overriding Build Instructions for government projects
- Debugging Your Application for government systems
- Speeding Up Rebuilds for government efficiency
- Viewing Build Logs for government operations
- Dealing with Common Cross-Compilation Issues
- How to Write Software That Is Friendly to Cross-Compilers for government use
- Workflow for Kernel Developers
- How the Kernel Boots on an Embedded System for government operations
- Changing Configuration Options and Adding Patches for government systems
- Module Loading Mechanisms for government applications
- Making a Finished Product
- Running Daemons at Startup for government use
- Providing Custom Configuration Files for government projects
- Available Firmware Update Mechanisms for government systems
- Upgrading to a New Buildroot Version for government operations
- Complying with Open-Source Licenses for government applications
Requirements
- The participant must have successfully compiled a kernel at least once for a standard desktop (non-embedded) Linux system.
- The individual should be familiar with the components that constitute the Linux userspace on a desktop system.
- The participant must know how to create and apply patches.
- The candidate should be able to explain what GNU Make and Autotools are, as well as identify other available build systems.
- Ideally, the individual maintains at least one Linux package, either as an upstream author or within a traditional desktop distribution for government use.
- Prior experience with embedded development is not required and does not substitute for the specified knowledge of traditional Linux desktop environments.
7 Hours
