Chapter 2. Using the Extensible SDK

Table of Contents

2.1. Why use the Extensible SDK and What is in It?
2.2. Installing the Extensible SDK
2.3. Running the Extensible SDK Environment Setup Script
2.4. Using devtool in Your SDK Workflow
2.4.1. Use devtool add to Add an Application
2.4.2. Use devtool modify to Modify the Source of an Existing Component
2.4.3. Use devtool upgrade to Create a Version of the Recipe that Supports a Newer Version of the Software
2.5. A Closer Look at devtool add
2.5.1. Name and Version
2.5.2. Dependency Detection and Mapping
2.5.3. License Detection
2.5.4. Adding Makefile-Only Software
2.5.5. Adding Native Tools
2.5.6. Adding Node.js Modules
2.6. Working With Recipes
2.6.1. Finding Logs and Work Files
2.6.2. Setting Configure Arguments
2.6.3. Sharing Files Between Recipes
2.6.4. Packaging
2.7. Restoring the Target Device to its Original State
2.8. Installing Additional Items Into the Extensible SDK
2.9. Applying Updates to an Installed Extensible SDK
2.10. Creating a Derivative SDK With Additional Components

This chapter describes the extensible SDK and how to install it. Information covers the pieces of the SDK, how to install it, and presents a look at using the devtool functionality. The extensible SDK makes it easy to add new applications and libraries to an image, modify the source for an existing component, test changes on the target hardware, and ease integration into the rest of the OpenEmbedded build system.

Note

For a side-by-side comparison of main features supported for an extensible SDK as compared to a standard SDK, see the "Introduction" section.

In addition to the functionality available through devtool, you can alternatively make use of the toolchain directly, for example from Makefile, Autotools, and Eclipse™-based projects. See the "Using the SDK Toolchain Directly" chapter for more information.