mirror of
https://git.yoctoproject.org/poky
synced 2026-01-29 21:08:42 +01:00
ae06e04cd2
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>
36 lines
1.9 KiB
HTML
36 lines
1.9 KiB
HTML
<html>
|
||
<head>
|
||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||
<title>3.1.2. Metadata (Recipes)</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="yocto-project-components.html" title="3.1. Yocto Project Components">
|
||
<link rel="prev" href="usingpoky-components-bitbake.html" title="3.1.1. BitBake">
|
||
<link rel="next" href="metadata-virtual-providers.html" title="3.1.3. Metadata (Virtual Providers)">
|
||
</head>
|
||
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.1.2. Metadata (Recipes)">
|
||
<div class="titlepage"><div><div><h3 class="title">
|
||
<a name="usingpoky-components-metadata"></a>3.1.2. Metadata (Recipes)</h3></div></div></div>
|
||
<p>
|
||
Files that have the <code class="filename">.bb</code> suffix are
|
||
"recipes" files.
|
||
In general, a recipe contains information about a single piece
|
||
of software.
|
||
This information includes the location from which to download
|
||
the unaltered source, any source patches to be applied to that
|
||
source (if needed), which special configuration options to
|
||
apply, how to compile the source files, and how to package the
|
||
compiled output.
|
||
</p>
|
||
<p>
|
||
The term "package" is sometimes used to refer to recipes.
|
||
However, since the word "package" is used for the packaged
|
||
output from the OpenEmbedded build system (i.e.
|
||
<code class="filename">.ipk</code> or <code class="filename">.deb</code> files),
|
||
this document avoids using the term "package" when referring
|
||
to recipes.
|
||
</p>
|
||
</div></body>
|
||
</html>
|