From 8eb6e7fcbf970d205ca06f1e80f7dc86fac083c6 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 8 Jan 2014 08:01:59 -0600 Subject: 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 Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 19 ++++++++++++------- 1 file 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 @@ - - When writing shell functions, you need to be aware of BitBake's - curly brace parsing. + + 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. - Here is an example that causes BitBake to produce a parsing + without leading spaces. + + + + Here is an example that causes BitBake to produce a parsing error: fakeroot create_shar() { @@ -1254,8 +1259,8 @@ } EOF } - - + +
-- cgit v1.2.3-54-g00ecf