generic-poky/documentation/ref-manual/eclipse/html/poky-ref-manual/build-overview.html

62 lines
3.5 KiB
HTML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>2.1.1. Build Overview</title>
<link rel="stylesheet" type="text/css" href="../book.css">
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
<link rel="up" href="usingpoky-build.html" title="2.1. Running a Build">
<link rel="prev" href="usingpoky-build.html" title="2.1. Running a Build">
<link rel="next" href="building-an-image-using-gpl-components.html" title="2.1.2. Building an Image Using GPL Components">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.1.1. Build Overview">
<div class="titlepage"><div><div><h3 class="title">
<a name="build-overview"></a>2.1.1. Build Overview</h3></div></div></div>
<p>
The first thing you need to do is set up the OpenEmbedded build environment by sourcing
the <a class="link" href="structure-core-script.html" title="5.1.10. oe-init-build-env">environment setup script</a> as follows:
</p>
<pre class="literallayout">
$ source oe-init-build-env [build_dir]
</pre>
<p>
</p>
<p>
The <code class="filename">build_dir</code> is optional and specifies the directory the
OpenEmbedded build system uses for the build -
the <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>.
If you do not specify a Build Directory it defaults to <code class="filename">build</code>
in your current working directory.
A common practice is to use a different Build Directory for different targets.
For example, <code class="filename">~/build/x86</code> for a <code class="filename">qemux86</code>
target, and <code class="filename">~/build/arm</code> for a <code class="filename">qemuarm</code> target.
See <a class="link" href="structure-core-script.html" title="5.1.10. oe-init-build-env">oe-init-build-env</a>
for more information on this script.
</p>
<p>
Once the build environment is set up, you can build a target using:
</p>
<pre class="literallayout">
$ bitbake &lt;target&gt;
</pre>
<p>
</p>
<p>
The <code class="filename">target</code> is the name of the recipe you want to build.
Common targets are the images in <code class="filename">meta/recipes-core/images</code>,
<code class="filename">/meta/recipes-sato/images</code>, etc. all found in the
<a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>.
Or, the target can be the name of a recipe for a specific piece of software such as
<span class="application">busybox</span>.
For more details about the images the OpenEmbedded build system supports, see the
"<a class="link" href="ref-images.html" title="Chapter 8. Images">Images</a>" chapter.
</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
Building an image without GNU General Public License Version 3 (GPLv3) components
is only supported for minimal and base images.
See the "<a class="link" href="ref-images.html" title="Chapter 8. Images">Images</a>" chapter for more information.
</div>
</div></body>
</html>