sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual: Edits to "Locate a Base Recipe" section. 

I removed the note structure for the information about BitBake
parcing curly braces.  The note was to prominent.  I added a
leading sentence to better integrate the information into the
section.

(From yocto-docs rev: 21dd7ceced2c9867e4fefc2aab81a4ab3da3bc7d)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2014-01-08 08:01:59 -06:00 committed by Richard Purdie
parent 1105b46d8f
commit 8eb6e7fcbf
1 changed files with 12 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -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'>