diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index b8669f8daa..8706bd6888 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1213,40 +1213,154 @@
-
- Locate a Base Recipe
+
+ Locate or Automatically Create a Base Recipe
- Before writing a recipe from scratch, it is often useful to
- discover whether someone else has already written one that
- meets (or comes close to meeting) your needs.
- The Yocto Project and OpenEmbedded communities maintain many
- recipes that might be candidates for what you are doing.
- You can find a good central index of these recipes in the
- OpenEmbedded metadata index.
+ You can always write a recipe from scratch.
+ However, two choices exist that can help you quickly get a
+ start on a new recipe:
+
+ recipetool:
+ A tool provided by the Yocto Project that automates
+ creation of a base recipe based on the source
+ files.
+
+ Existing Recipes:
+ Location and modification of an existing recipe that is
+ similar in function to the recipe you need.
+
+
-
- Working from an existing recipe or a skeleton recipe is the
- best way to get started.
- Here are some points on both methods:
-
- Locate and modify a recipe that
- is close to what you want to do:
- This method works when you are familiar with the
- current recipe space.
- The method does not work so well for those new to
- the Yocto Project or writing recipes.
- Some risks associated with this method are
- using a recipe that has areas totally unrelated to
- what you are trying to accomplish with your recipe,
- not recognizing areas of the recipe that you might
- have to add from scratch, and so forth.
- All these risks stem from unfamiliarity with the
- existing recipe space.
- Use and modify the following
- skeleton recipe:
-
+
+
+
+ Locating and Using a Similar Recipe
+
+
+ Before writing a recipe from scratch, it is often useful to
+ discover whether someone else has already written one that
+ meets (or comes close to meeting) your needs.
+ The Yocto Project and OpenEmbedded communities maintain many
+ recipes that might be candidates for what you are doing.
+ You can find a good central index of these recipes in the
+ OpenEmbedded metadata index.
+
+
+
+ Working from an existing recipe or a skeleton recipe is the
+ best way to get started.
+ Here are some points on both methods:
+
+ Locate and modify a recipe that
+ is close to what you want to do:
+ This method works when you are familiar with the
+ current recipe space.
+ The method does not work so well for those new to
+ the Yocto Project or writing recipes.
+ Some risks associated with this method are
+ using a recipe that has areas totally unrelated to
+ what you are trying to accomplish with your recipe,
+ not recognizing areas of the recipe that you might
+ have to add from scratch, and so forth.
+ All these risks stem from unfamiliarity with the
+ existing recipe space.
+ Use and modify the following
+ skeleton recipe:
+ If for some reason you do not want to use
+ recipetool and you cannot
+ find an existing recipe that is close to meeting
+ your needs, you can use the following structure to
+ provide the fundamental areas of a new recipe.
+
DESCRIPTION = ""
HOMEPAGE = ""
LICENSE = ""
@@ -1255,14 +1369,11 @@
LIC_FILES_CHKSUM = ""
SRC_URI = ""
-
- Modifying this recipe is the recommended method for
- creating a new recipe.
- The recipe provides the fundamental areas that you need
- to include, exclude, or alter to fit your needs.
-
-
-
+
+
+
+
+