Scott Rifenbark ed0a240e16 documentation: Rename of poky-ref-manual folder to ref-manual.
Changing the folder that holds the YP Reference Manual to be
"ref-manual".  This will help with confustion over the manual's
intended purpose.

(From yocto-docs rev: 1106442964b5080cb0b6b3bd3af32e9407c0f7c1)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-07 14:43:25 +00:00

34 lines
1.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.2. build/</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-bitbake.html" title="5.1.1. bitbake/">
<link rel="next" href="handbook.html" title="5.1.3. documentation">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.1.2. build/">
<div class="titlepage"><div><div><h3 class="title">
<a name="structure-core-build"></a>5.1.2. <code class="filename">build/</code>
</h3></div></div></div>
<p>
This directory contains user configuration files and the output
generated by the OpenEmbedded build system in its standard configuration where
the source tree is combined with the output.
The <a class="link" href="../dev-manual/build-directory.html" target="_self">Build Directory</a>
is created initially when you <code class="filename">source</code>
the OpenEmbedded build environment setup script <code class="filename">oe-init-build-env</code>.
</p>
<p>
It is also possible to place output and configuration
files in a directory separate from the
<a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>
by providing a directory name when you <code class="filename">source</code>
the setup script.
For information on separating output from your local Source Directory files, see <a class="link" href="structure-core-script.html" title="5.1.10. oe-init-build-env">oe-init-build-env</a>.
</p>
</div></body>
</html>