mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-06-01 13:09:50 +00:00
Code Issues Projects Releases Wiki Activity

toaster-manual: Updated the "Configuring Toaster" section

Browse Source 
Updated with review edits.

(From yocto-docs rev: 43dc539fb195e6194117dbc4de4d053fff53e9ff)

Signed-off-by: Kristi Rifenbark <kristi.rifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Kristi Rifenbark
2017-10-13 13:24:02 -07:00
committed by Richard Purdie
parent 332e309030
commit 4e818ce297
1 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/toaster-manual/toaster-manual-reference.xml
+9 -1
View File
@@ -316,6 +316,9 @@
For example, you can add one or more additional selections that For example, you can add one or more additional selections that
present custom layer sets or distros, and any other local or proprietary present custom layer sets or distros, and any other local or proprietary
content. content.
</para>
<para>
Additionally, you can completely disable the content from the Additionally, you can completely disable the content from the
<filename>oe-core.xml</filename> and <filename>poky.xml</filename> <filename>oe-core.xml</filename> and <filename>poky.xml</filename>
files by defining the section shown below in the files by defining the section shown below in the
@@ -331,7 +334,6 @@
<literallayout class='monospaced'> <literallayout class='monospaced'>
&lt;object model="orm.toastersetting" pk="99"&gt; &lt;object model="orm.toastersetting" pk="99"&gt;
&lt;field type="CharField" name="name"&gt;CUSTOM_XML_ONLY&lt;/field&gt; &lt;field type="CharField" name="name"&gt;CUSTOM_XML_ONLY&lt;/field&gt;
&lt;field type="CharField" name="value"&gt;True&lt;/field&gt; &lt;field type="CharField" name="value"&gt;True&lt;/field&gt;
&lt;/object&gt; &lt;/object&gt;
</literallayout> </literallayout>
@@ -447,6 +449,12 @@
Layer definitions are the most complex. Layer definitions are the most complex.
The following defines each of the layers, and then defines the exact layer The following defines each of the layers, and then defines the exact layer
version of the layer used for each respective release. version of the layer used for each respective release.
You must have one <filename>orm.layer</filename>
entry for each layer.
Then, with each entry you need a set of
<filename>orm.layer_version</filename> entries that connects
the layer with each release that includes the layer.
In general all releases include the layer.
<literallayout class='monospaced'> <literallayout class='monospaced'>
&lt;object model="orm.layer" pk="1"&gt; &lt;object model="orm.layer" pk="1"&gt;
&lt;field type="CharField" name="name"&gt;openembedded-core&lt;/field&gt; &lt;field type="CharField" name="name"&gt;openembedded-core&lt;/field&gt;