From 134c76e4819ba8ee94717e75e350cbd24fca4ebf Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 25 Nov 2013 06:28:36 -0800 Subject: 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 (From yocto-docs rev: 74b7a193e8356931e5a0db2ea76b4543880ed2ec) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'documentation/dev-manual') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 6b6044503c..fdab97dd86 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1960,14 +1960,14 @@ To use the menuconfig 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 &OE_INIT_FILE; or oe-init-build-env-memres script found in the Build Directory. - The following commands build and invoke menuconfig assuming the + The following commands run menuconfig assuming the Source Directory top-level folder is ~/poky: @@ -1989,7 +1989,7 @@ Thus, the following commands from the shell in which you previously sourced the environment initialization script cleans the shared state cache and the WORKDIR - directory and then builds and launches menuconfig: + directory and then runs menuconfig: $ bitbake linux-yocto -c menuconfig -- cgit v1.2.3-54-g00ecf