From 4e818ce29742ce6cd9f54ebb27f045a25d99044d Mon Sep 17 00:00:00 2001 From: Kristi Rifenbark Date: Fri, 13 Oct 2017 13:24:02 -0700 Subject: toaster-manual: Updated the "Configuring Toaster" section Updated with review edits. (From yocto-docs rev: 43dc539fb195e6194117dbc4de4d053fff53e9ff) Signed-off-by: Kristi Rifenbark Signed-off-by: Richard Purdie --- .../toaster-manual/toaster-manual-reference.xml | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/documentation/toaster-manual/toaster-manual-reference.xml b/documentation/toaster-manual/toaster-manual-reference.xml index 7c5b844d8a..665dc15ffb 100644 --- a/documentation/toaster-manual/toaster-manual-reference.xml +++ b/documentation/toaster-manual/toaster-manual-reference.xml @@ -316,6 +316,9 @@ For example, you can add one or more additional selections that present custom layer sets or distros, and any other local or proprietary content. + + + Additionally, you can completely disable the content from the oe-core.xml and poky.xml files by defining the section shown below in the @@ -331,7 +334,6 @@ <object model="orm.toastersetting" pk="99"> <field type="CharField" name="name">CUSTOM_XML_ONLY</field> - <field type="CharField" name="value">True</field> </object> @@ -342,15 +344,15 @@ Understanding Fixture File Format - The following is an overview of the file format used by the + The following is an overview of the file format used by the oe-core.xml, poky.xml, and custom.xml files. - The following subsections describe each of the sections in the + The following subsections describe each of the sections in the fixture files, and outline an example section of the XML code. - you can use to help understand this information and create a local + you can use to help understand this information and create a local custom.xml file. @@ -447,6 +449,12 @@ Layer definitions are the most complex. The following defines each of the layers, and then defines the exact layer version of the layer used for each respective release. + You must have one orm.layer + entry for each layer. + Then, with each entry you need a set of + orm.layer_version entries that connects + the layer with each release that includes the layer. + In general all releases include the layer. <object model="orm.layer" pk="1"> <field type="CharField" name="name">openembedded-core</field> -- cgit v1.2.3-54-g00ecf