From 4abc384f253fab140324ac9e243b000dc5d6ae8c Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 19 Nov 2013 13:55:17 -0800 Subject: [PATCH] dev-manual: Some review edits to the new writing a recipe section. (From yocto-docs rev: 06287769f9a1fc0beb1a867ceb22922e35452589) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-common-tasks.xml | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 762ffb2399..2e011724c3 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1142,9 +1142,8 @@ Recipes (.bb files) are fundamental components in the Yocto Project environment. - The OpenEmbedded build system parses and compiles your recipes and - packages the output to create an image. - Your project consists in part of the recipes that define it. + Each software component built by the OpenEmbedded build system + requires a recipe to define the component. This section describes how to create, write, and test a new recipe. @@ -1199,7 +1198,7 @@ The first thing your recipe must do is fetch the source files. - Fetching is accomplished through the + Fetching is controlled mainly through the SRC_URI variable. Your recipe must have a SRC_URI variable @@ -1218,10 +1217,12 @@ - You need to use an instance of the SRC_URI - variable for each unique location holding your source file. - For example, if you need a tarball, and two patches, then you - need to use three instances of the variable in your recipe. + The instance (or instances) of the SRC_URI + variable in your recipe must define each unique location + for your source files. + For example, if you need a tarball, and two patches, then your + SRC_URI statement(s) must point to the + tarball and the patches.