Files
poky/documentation/getting-started/eclipse/html/getting-started/distro-layer.html
Scott Rifenbark ae06e04cd2 documentation: Created new "Getting Started" manual.
Creation involved removing the overview-manual and replacing it
with the getting-started manual.  All links to the string
"&YOCTO_DOCS_OVERVIEW_URL" had to be replaced with
"&YOCTO_DOCS_GS_URL" across the entire YP manual set.  I renamed
files used to create the manual with prefixes suited for the
new manual name, which is "Getting Started With Yocto Project".

The style sheet for the new manual needed updating to display the
new .PNG image for the title page.  The mega-manual file had to
be updated to include the files.  The mega-manual.sed file had
to be updated to include the new manual and not use the overview
manual.

(From yocto-docs rev: 6c7abf9192390121000f577d6c98f259d290d15d)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-14 15:25:29 +00:00

61 lines
3.4 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.8.2.1. Distro Layer</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="Getting Started With Yocto Project">
<link rel="up" href="metadata-machine-configuration-and-policy-configuration.html" title="2.8.2. Metadata, Machine Configuration, and Policy Configuration">
<link rel="prev" href="metadata-machine-configuration-and-policy-configuration.html" title="2.8.2. Metadata, Machine Configuration, and Policy Configuration">
<link rel="next" href="bsp-layer.html" title="2.8.2.2. BSP Layer">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.8.2.1. Distro Layer">
<div class="titlepage"><div><div><h4 class="title">
<a name="distro-layer"></a>2.8.2.1. Distro Layer</h4></div></div></div>
<p>
The distribution layer provides policy configurations for your
distribution.
Best practices dictate that you isolate these types of
configurations into their own layer.
Settings you provide in
<code class="filename">conf/distro/<em class="replaceable"><code>distro</code></em>.conf</code> override
similar
settings that BitBake finds in your
<code class="filename">conf/local.conf</code> file in the Build
Directory.
</p>
<p>
The following list provides some explanation and references
for what you typically find in the distribution layer:
</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem"><p><span class="emphasis"><em>classes:</em></span>
Class files (<code class="filename">.bbclass</code>) hold
common functionality that can be shared among
recipes in the distribution.
When your recipes inherit a class, they take on the
settings and functions for that class.
You can read more about class files in the
"<a class="link" href="../ref-manual/ref-classes.html" target="_self">Classes</a>"
section of the Yocto Reference Manual.
</p></li>
<li class="listitem"><p><span class="emphasis"><em>conf:</em></span>
This area holds configuration files for the
layer (<code class="filename">conf/layer.conf</code>),
the distribution
(<code class="filename">conf/distro/<em class="replaceable"><code>distro</code></em>.conf</code>),
and any distribution-wide include files.
</p></li>
<li class="listitem"><p><span class="emphasis"><em>recipes-*:</em></span>
Recipes and append files that affect common
functionality across the distribution.
This area could include recipes and append files
to add distribution-specific configuration,
initialization scripts, custom image recipes,
and so forth.</p></li>
</ul></div>
<p>
</p>
</div></body>
</html>