generic-poky/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-core-script.html

54 lines
2.9 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>5.1.10. oe-init-build-env</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="structure-core.html" title="5.1. Top level core components">
<link rel="prev" href="structure-core-scripts.html" title="5.1.9. scripts/">
<link rel="next" href="structure-basic-top-level.html" title="5.1.11. LICENSE, README, and README.hardware">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.10. oe-init-build-env">
<div class="titlepage"><div><div><h3 class="title">
<a name="structure-core-script"></a>5.1.10. <code class="filename">oe-init-build-env</code>
</h3></div></div></div>
<p>
This script sets up the OpenEmbedded build environment.
Running this script with the <code class="filename">source</code> command in
a shell makes changes to <code class="filename">PATH</code> and sets other core BitBake variables based on the
current working directory.
You need to run this script before running BitBake commands.
The script uses other scripts within the <code class="filename">scripts</code> directory to do
the bulk of the work.
</p>
<p>
By default, running this script without a Build Directory argument creates the
<code class="filename">build</code> directory.
If you provide a Build Directory argument when you <code class="filename">source</code>
the script, you direct OpenEmbedded build system to create a
<a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a> of your choice.
For example, the following command creates a Build Directory named
<code class="filename">mybuilds</code> that is outside of the
<a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>:
</p>
<pre class="literallayout">
$ source oe-init-build-env ~/mybuilds
</pre>
<p>
</p>
<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
The OpenEmbedded build system does not support file or directory names that
contain spaces.
If you attempt to run the <code class="filename">oe-init-build-env</code> script
from a Source Directory that contains spaces in either the filenames
or directory names, the script returns an error indicating no such
file or directory.
Be sure to use a Source Directory free of names containing spaces.
</div>
<p>
</p>
</div></body>
</html>