4. Application Development | Embedded Linux Projects Using Yocto Project Cookbook

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents

Embedded Linux Projects Using Yocto Project Cookbook

By : Alex González

4.4 (13)

Embedded Linux Projects Using Yocto Project Cookbook

4.4 (13)

By: Alex González

Overview of this book

If you are an embedded developer learning about embedded Linux with some experience with the Yocto project, this book is the ideal way to become proficient and broaden your knowledge with examples that are immediately applicable to your embedded developments. Experienced embedded Yocto developers will find new insight into working methodologies and ARM specific development competence.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Sections

Conventions

Reader feedback

Customer support

Free Chapter

1. The Build System

1. The Build System

Introduction

Setting up the host system

Installing Poky

Creating a build directory

Building your first image

Explaining the Freescale Yocto ecosystem

Installing support for Freescale hardware

Building Wandboard images

Troubleshooting your Wandboard's first boot

Configuring network booting for a development setup

Sharing downloads

Sharing the shared state cache

Setting up a package feed

Using build history

Working with build statistics

Debugging the build system

2. The BSP Layer

2. The BSP Layer

Introduction

Creating a custom BSP layer

Introducing system development workflows

Adding a custom kernel and bootloader

Building the U-Boot bootloader

Explaining Yocto's Linux kernel support

Describing Linux's build system

Configuring the Linux kernel

Building the Linux kernel

Building external kernel modules

Debugging the Linux kernel and modules

Debugging the Linux kernel booting process

Using the kernel function tracing system

Managing the device tree

Debugging device tree issues

3. The Software Layer

3. The Software Layer

Introduction

Exploring an image's contents

Adding a new software layer

Selecting a specific package version and providers

Adding supported packages

Adding new packages

Adding data, scripts, or configuration files

Managing users and groups

Using the sysvinit initialization manager

Using the systemd initialization manager

Installing package-installation scripts

Reducing the Linux kernel image size

Reducing the root filesystem image size

Releasing software

Analyzing your system for compliance

Working with open source and proprietary code

4. Application Development

4. Application Development

Introduction

Introducing toolchains

Preparing and using an SDK

Using the Application Development Toolkit

Using the Eclipse IDE

Developing GTK+ applications

Using the Qt Creator IDE

Developing Qt applications

Describing workflows for application development

Working with GNU make

Working with the GNU build system

Working with the CMake build system

Working with the SCons builder

Developing with libraries

Working with the Linux framebuffer

Using the X Windows system

Using Wayland

Adding Python applications

Integrating the Oracle Java Runtime Environment

Integrating the Open Java Development Kit

Integrating Java applications

5. Debugging, Tracing, and Profiling

5. Debugging, Tracing, and Profiling

Introduction

Analyzing core dumps

Native GDB debugging

Cross GDB debugging

Using strace for application debugging

Using the kernel's performance counters

Using static kernel tracing

Using dynamic kernel tracing

Using dynamic kernel events

Exploring Yocto's tracing and profiling tools

Tracing and profiling with perf

Using SystemTap

Using OProfile

Using LTTng

Using blktrace

Index

Index

Developing with libraries

Most applications make use of shared libraries, which saves system memory and disk space, as they are shared between different applications. Modularizing code into libraries also allows for easier versioning and code management.

This recipe will explain how to work with both static and shared libraries in Linux and Yocto.

Getting ready

By convention, library files start with the lib prefix.

There are basically two library types:

Static libraries (.a): When the object code is linked and becomes part of the application
Dynamic libraries (.so): Linked at compile time but not included in the application, so they need to be available at runtime. Multiple applications can share a dynamic library so they need less disk space.

Libraries are placed in the following standard root filesystem locations:

/lib: Libraries required for startup
/usr/lib: Most system libraries
/usr/local/lib: Non-system libraries

Dynamic libraries follow certain naming conventions on running systems so that...

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Embedded Linux Projects Using Yocto Project Cookbook

Search

Your notes and bookmarks