diff options
author | Scott Rifenbark <srifenbark@gmail.com> | 2016-09-22 07:56:25 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-09-28 15:02:32 +0100 |
commit | b8ad433ff3bc2086524a7c6281f2a528386ff405 (patch) | |
tree | 81e79d2e3f48acaa466d9bcce19d7bc77f735b2a /documentation/dev-manual | |
parent | 285931e0d4d6cd6d2a7bab68c55797df3f64cf1e (diff) | |
download | poky-b8ad433ff3bc2086524a7c6281f2a528386ff405.tar.gz |
dev-manual: Applied review edits to the "writing new recipe"
Applied various edits to the "Writing a New Recipe" section.
Several nits.
(From yocto-docs rev: 17818ff89805e0df3a0445f64a4f9133550fa7d0)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 19 |
1 files changed, 9 insertions, 10 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 9521c7cd56..3024252b76 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml | |||
@@ -1260,11 +1260,11 @@ | |||
1260 | <listitem><para> | 1260 | <listitem><para> |
1261 | <emphasis><filename>devtool add</filename>:</emphasis> | 1261 | <emphasis><filename>devtool add</filename>:</emphasis> |
1262 | A command that assists in creating a recipe and | 1262 | A command that assists in creating a recipe and |
1263 | an environment condusive to development. | 1263 | an environment conducive to development. |
1264 | </para></listitem> | 1264 | </para></listitem> |
1265 | <listitem><para> | 1265 | <listitem><para> |
1266 | <emphasis><filename>recipetool</filename>:</emphasis> | 1266 | <emphasis><filename>recipetool create</filename>:</emphasis> |
1267 | A tool provided by the Yocto Project that automates | 1267 | A command provided by the Yocto Project that automates |
1268 | creation of a base recipe based on the source | 1268 | creation of a base recipe based on the source |
1269 | files. | 1269 | files. |
1270 | </para></listitem> | 1270 | </para></listitem> |
@@ -1294,18 +1294,17 @@ | |||
1294 | <para> | 1294 | <para> |
1295 | You can find a complete description of the | 1295 | You can find a complete description of the |
1296 | <filename>devtool add</filename> command in the | 1296 | <filename>devtool add</filename> command in the |
1297 | "<ulink url='&YOCTO_DOCS_SDK_URL;#sdk-use-devtool-to-add-an-application'>Use <filename>devtool add</filename> to Add an Application</ulink>" | 1297 | "<link linkend='use-devtool-to-integrate-new-code'>Use <filename>devtool add</filename> to Add an Application</link>" |
1298 | section in the Yocto Project Software Development Kit (SDK) | 1298 | section. |
1299 | Developer's Guide. | ||
1300 | </para> | 1299 | </para> |
1301 | </section> | 1300 | </section> |
1302 | 1301 | ||
1303 | <section id='new-recipe-creating-the-base-recipe-using-recipetool'> | 1302 | <section id='new-recipe-creating-the-base-recipe-using-recipetool'> |
1304 | <title>Creating the Base Recipe Using <filename>recipetool</filename></title> | 1303 | <title>Creating the Base Recipe Using <filename>recipetool create</filename></title> |
1305 | 1304 | ||
1306 | <para> | 1305 | <para> |
1307 | <filename>recipetool</filename> automates creation of | 1306 | <filename>recipetool create</filename> automates creation |
1308 | a base recipe given a set of source code files. | 1307 | of a base recipe given a set of source code files. |
1309 | As long as you can extract or point to the source files, | 1308 | As long as you can extract or point to the source files, |
1310 | the tool will construct a recipe and automatically | 1309 | the tool will construct a recipe and automatically |
1311 | configure all pre-build information into the recipe. | 1310 | configure all pre-build information into the recipe. |
@@ -1832,7 +1831,7 @@ | |||
1832 | The quickest way to find this path is to have BitBake return it | 1831 | The quickest way to find this path is to have BitBake return it |
1833 | by running the following: | 1832 | by running the following: |
1834 | <literallayout class='monospaced'> | 1833 | <literallayout class='monospaced'> |
1835 | $ bitbake -e recipename | grep ^WORKDIR= | 1834 | $ bitbake -e <replaceable>basename</replaceable> | grep ^WORKDIR= |
1836 | </literallayout> | 1835 | </literallayout> |
1837 | As an example, assume a Source Directory top-level folder named | 1836 | As an example, assume a Source Directory top-level folder named |
1838 | <filename>poky</filename>, a default Build Directory at | 1837 | <filename>poky</filename>, a default Build Directory at |