From cd041b7546f3b22a0d503c8cabc9f3d5fdbdee1a Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 24 Feb 2016 15:02:23 -0800 Subject: dev-manual: Applied review comments to the devshell section. Applied better wording to a couple areas in this section as pointed out by the review. Fixes [YOCTO #9114] (From yocto-docs rev: f5a402aa08b102c767e112d8df05041650733d54) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-model.xml | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) (limited to 'documentation/dev-manual/dev-manual-model.xml') diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index d10f85f6a1..984d08df81 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -3236,9 +3236,13 @@ When debugging certain commands or even when just editing packages, devshell can be a useful tool. - When you invoke devshell, source files are - extracted into your working directory and patches are applied. - Then, a new terminal is opened and you are placed in the working directory. + When you invoke devshell, all tasks up to and + including + do_patch + are run for the specified target. + Then, a new terminal is opened and you are placed in + ${S}, + the source directory. In the new terminal, all the OpenEmbedded build-related environment variables are still defined so you can use commands such as configure and make. @@ -3286,7 +3290,8 @@ run the corresponding run.* script in the ${WORKDIR}/temp - (e.g., run.do_configure.pid). + directory (e.g., + run.do_configure.pid). If a task's script does not exist, which would be the case if the task was skipped by way of the sstate cache, you can create the task by first running it outside of the devshell: -- cgit v1.2.3-54-g00ecf