dev-manual: Re-worded menuconfig preparation

Rather than saying menuconfig is "built", I changed the text to say
it is "run."

Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: f95b945787c84edb532c24886cdd44f1bc8bd98a)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-11-25 06:28:36 -08:00 committed by Richard Purdie
parent 18c59735d7
commit 21ea9bced3
1 changed files with 3 additions and 3 deletions

View File

@ -2691,14 +2691,14 @@ the details.
<para>
To use the <filename>menuconfig</filename> tool in the Yocto Project development
environment, you must build the tool using BitBake.
environment, you must launch it using BitBake.
Thus, the environment must be set up using the
<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>
or
<ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>
script found in the
<link linkend='build-directory'>Build Directory</link>.
The following commands build and invoke <filename>menuconfig</filename> assuming the
The following commands run <filename>menuconfig</filename> assuming the
<link linkend='source-directory'>Source Directory</link>
top-level folder is <filename>~/poky</filename>:
<literallayout class='monospaced'>
@ -2720,7 +2720,7 @@ the details.
Thus, the following commands from the shell in which you previously sourced the
environment initialization script cleans the shared state cache and the
<ulink url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ulink>
directory and then builds and launches <filename>menuconfig</filename>:
directory and then runs <filename>menuconfig</filename>:
<literallayout class='monospaced'>
$ bitbake linux-yocto -c menuconfig
</literallayout>