summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml19
1 files changed, 12 insertions, 7 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 3e9ccce..0b9bb6b 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1221,16 +1221,21 @@
</itemizedlist>
</para>
- <note>
- <para>When writing shell functions, you need to be aware of BitBake's
- curly brace parsing.
+ <para>
+ Regardless of where you get a base recipe, you will need to
+ make changes to support your needs.
+ When you do, you need to be aware of how BitBake parses curly
+ braces.
If a recipe uses a closing curly brace within the function and
the character has no leading spaces, BitBake produces a parsing
error.
If you use a pair of curly brace in a shell function, the
closing curly brace must not be located at the start of the line
- without leading spaces.</para>
- <para>Here is an example that causes BitBake to produce a parsing
+ without leading spaces.
+ </para>
+
+ <para>
+ Here is an example that causes BitBake to produce a parsing
error:
<literallayout class='monospaced'>
fakeroot create_shar() {
@@ -1254,8 +1259,8 @@
}
EOF
}
- </literallayout></para>
- </note>
+ </literallayout>
+ </para>
</section>
<section id='new-recipe-naming-the-recipe'>
OpenPOWER on IntegriCloud