mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-04-26 00:32:12 +02:00
Code Issues Packages Projects Releases Wiki Activity

sdk-manual: Added links to sample tasks to "Working With Recipes"

Browse Source 
(From yocto-docs rev: 4c59f516de8edff7eb9ae27194c9af27a853dfa9)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2018-05-31 11:10:40 -07:00
committed by Richard Purdie
parent 6e9bfc5901
commit 1e3fedacb3
1 changed files with 18 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
documentation/sdk-manual/sdk-extensible.xml
View File

@@ -1393,8 +1393,9 @@
<title>Working With Recipes</title>
<para>
When building a recipe with <filename>devtool build</filename>, the
typical build progression is as follows:
When building a recipe using the
<filename>devtool build</filename> command, the typical build
progresses as follows:
<orderedlist>
<listitem><para>
Fetch the source
@@ -1406,7 +1407,7 @@
Configure the source
</para></listitem>
<listitem><para>
Compiling the source
Compile the source
</para></listitem>
<listitem><para>
Install the build output
@@ -1417,10 +1418,13 @@
</orderedlist>
For recipes in the workspace, fetching and unpacking is disabled
as the source tree has already been prepared and is persistent.
Each of these build steps is defined as a function, usually with a
"do_" prefix.
These functions are typically shell scripts but can instead be written
in Python.
Each of these build steps is defined as a function (task), usually
with a "do_" prefix (e.g.
<ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-fetch'><filename>do_fetch</filename></ulink>,
<ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-unpack'><filename>do_unpack</filename></ulink>,
and so forth).
These functions are typically shell scripts but can instead be
written in Python.
</para>
<para>
@@ -1428,12 +1432,13 @@
recipe does not include complete instructions for building the
software.
Instead, common functionality is encapsulated in classes inherited
with the <filename>inherit</filename> directive, leaving the recipe
to describe just the things that are specific to the software to be
built.
A <ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-base'><filename>base</filename></ulink>
class exists that is implicitly inherited by all recipes and provides
the functionality that most typical recipes need.
with the <filename>inherit</filename> directive.
This technique leaves the recipe to describe just the things that
are specific to the software being built.
A
<ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-base'><filename>base</filename></ulink>
class exists that is implicitly inherited by all recipes and
provides the functionality that most recipes typically need.
</para>
<para>