diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-01-08 08:01:59 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-01-21 21:57:57 +0000 |
commit | 8eb6e7fcbf970d205ca06f1e80f7dc86fac083c6 (patch) | |
tree | 2fd7cc411b8b63503d9668759ed9b4b342ed085a /documentation | |
parent | 1105b46d8f0174edbc315370835546e8ba5f7fd9 (diff) | |
download | poky-8eb6e7fcbf970d205ca06f1e80f7dc86fac083c6.tar.gz |
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>
Diffstat (limited to 'documentation')
-rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 19 |
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 3e9cccef15..0b9bb6bec5 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml | |||
@@ -1221,16 +1221,21 @@ | |||
1221 | </itemizedlist> | 1221 | </itemizedlist> |
1222 | </para> | 1222 | </para> |
1223 | 1223 | ||
1224 | <note> | 1224 | <para> |
1225 | <para>When writing shell functions, you need to be aware of BitBake's | 1225 | Regardless of where you get a base recipe, you will need to |
1226 | curly brace parsing. | 1226 | make changes to support your needs. |
1227 | When you do, you need to be aware of how BitBake parses curly | ||
1228 | braces. | ||
1227 | If a recipe uses a closing curly brace within the function and | 1229 | If a recipe uses a closing curly brace within the function and |
1228 | the character has no leading spaces, BitBake produces a parsing | 1230 | the character has no leading spaces, BitBake produces a parsing |
1229 | error. | 1231 | error. |
1230 | If you use a pair of curly brace in a shell function, the | 1232 | If you use a pair of curly brace in a shell function, the |
1231 | closing curly brace must not be located at the start of the line | 1233 | closing curly brace must not be located at the start of the line |
1232 | without leading spaces.</para> | 1234 | without leading spaces. |
1233 | <para>Here is an example that causes BitBake to produce a parsing | 1235 | </para> |
1236 | |||
1237 | <para> | ||
1238 | Here is an example that causes BitBake to produce a parsing | ||
1234 | error: | 1239 | error: |
1235 | <literallayout class='monospaced'> | 1240 | <literallayout class='monospaced'> |
1236 | fakeroot create_shar() { | 1241 | fakeroot create_shar() { |
@@ -1254,8 +1259,8 @@ | |||
1254 | } | 1259 | } |
1255 | EOF | 1260 | EOF |
1256 | } | 1261 | } |
1257 | </literallayout></para> | 1262 | </literallayout> |
1258 | </note> | 1263 | </para> |
1259 | </section> | 1264 | </section> |
1260 | 1265 | ||
1261 | <section id='new-recipe-naming-the-recipe'> | 1266 | <section id='new-recipe-naming-the-recipe'> |