Book Image

Embedded Linux Development Using Yocto Project Cookbook - Second Edition

By : Alex Gonzalez
Book Image

Embedded Linux Development Using Yocto Project Cookbook - Second Edition

By: Alex Gonzalez

Overview of this book

The Yocto Project has become the de facto distribution build framework for reliable and robust embedded systems with a reduced time to market.You'll get started by working on a build system where you set up Yocto, create a build directory, and learn how to debug it. Then, you'll explore everything about the BSP layer, from creating a custom layer to debugging device tree issues. In addition to this, you’ll learn how to add a new software layer, packages, data, scripts, and configuration files to your system. You will then cover topics based on application development, such as using the Software Development Kit and how to use the Yocto project in various development environments. Toward the end, you will learn how to debug, trace, and profile a running system. This second edition has been updated to include new content based on the latest Yocto release.
Table of Contents (13 chapters)
Title Page
Packt Upsell

Integrating Node.js applications

Node.js is a MIT-licensed open source JavaScript runtime environment. Built on Chrome's JavaScript Runtime (v8), it is an event-driven, non-blocking, and lightweight framework, initially mostly used to produce dynamic web content but currently used in a wide variety of applications, from scripting to HTML5 user interfaces. This recipe will show how to add Node.js applications to a target image.

Getting ready

Node.js has its own package manager, Node Packaged Modules (npm), which allows you to install third party modules and their dependencies. Modules are either installed locally, inside a directory, or globally, that is, on a location typically available as part of your path so they can be globally accessed.

Most Node.js applications make extensive use of modules. A module is basically application code described by a package.json file. The code and packages.json files can be in a directory, a Git repository, a compressed tarball, or a URI to a compressed tarball...