mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 12:29:55 +00:00
Code Issues Projects Releases Wiki Activity

ref-manual: Updates to native.bbclass

Browse Source 
Fixes [YOCTO #12924]

Naming convention does not apply to the second recipe-creation
method described in this class.  I have moved the note about that
to be under the applicable method (i.e. the first bullet).

Fixed the syntax reversal of the sample name in the example.

(From yocto-docs rev: f7f1a89043156527fa4b426c0322ad225a9f2ff1)

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-09-26 13:19:10 -07:00
committed by Richard Purdie
parent a2d14e5b6d
commit 6d9de01c18
1 changed files with 21 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/ref-manual/ref-classes.xml
+21 -15
View File
@@ -2173,8 +2173,9 @@ This check was removed for YP 2.3 release
<para>
The <filename>native</filename> class provides common
functionality for recipes that wish to build tools to run on the build
host (i.e. tools that use the compiler or other tools from the
functionality for recipes that build tools to run on the
<link linkend='hardware-build-system-term'>build host</link>
(i.e. tools that use the compiler or other tools from the
build host).
</para>
@@ -2182,30 +2183,35 @@ This check was removed for YP 2.3 release
You can create a recipe that builds tools that run natively on the
host a couple different ways:
<itemizedlist>
<listitem><para>Create a <replaceable>myrecipe</replaceable><filename>-native.bb</filename>
that inherits the <filename>native</filename> class.
<listitem><para>
Create a
<replaceable>myrecipe</replaceable><filename>-native.bb</filename>
recipe that inherits the <filename>native</filename> class.
If you use this method, you must order the inherit statement
in the recipe after all other inherit statements so that the
<filename>native</filename> class is inherited last.
<note><title>Warning</title>
When creating a recipe this way, the recipe name must
follow this naming convention:
<literallayout class='monospaced'>
<replaceable>myrecipe</replaceable>-native.bb
</literallayout>
Not using this naming convention can lead to subtle
problems caused by existing code that depends on that
naming convention.
</note>
</para></listitem>
<listitem><para>Create or modify a target recipe that contains
the following:
<listitem><para>
Create or modify a target recipe that contains the following:
<literallayout class='monospaced'>
<link linkend='var-BBCLASSEXTEND'><filename>BBCLASSEXTEND</filename></link> = "native"
</literallayout>
Inside the recipe, use <filename>_class-native</filename> and
<filename>_class-target</filename> overrides to specify any
functionality specific to the respective native or target
case.</para></listitem>
case.
</para></listitem>
</itemizedlist>
<note><title>Warning</title>
When creating a recipe, you must follow this naming convention:
<literallayout class='monospaced'>
native-<replaceable>myrecipe</replaceable>.bb
</literallayout>
Not doing so can lead to subtle problems because code exists
that depends on the naming convention.
</note>
</para>
<para>