From 2199b68fc88cd7f34fda7ad49bd50ca5176e0f5b Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 26 Sep 2016 08:35:56 -0700 Subject: [PATCH] dev-manual: Updated the devpyshell section Fixes [YOCTO #9166] I applied some review comments to the section. Pulled some stuff out that did not apply.pdated the devpyshell section (From yocto-docs rev: 7300358570de4da94ff5f22afd30128ef8dd0f13) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-model.xml | 89 +------------------ 1 file changed, 4 insertions(+), 85 deletions(-) diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 6f359c2986..1008e11696 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -1606,12 +1606,7 @@ 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. + Then a new terminal is opened. Additionally, key Python objects and code are available in the same way they are to BitBake tasks, in particular, the data store 'd'. So, commands such as the following are useful when exploring the data @@ -1650,86 +1645,10 @@ - For spawned terminals, the following occurs: - - The PATH variable includes the - cross-toolchain. - The pkgconfig variables find the correct - .pc files. - The configure command finds the - Yocto Project site files as well as any other necessary files. - + When you are finished using devpyshell, you + can exit the shell either by using Ctrl+d or closing the terminal + window. - - - Within this environment, you can run configure or compile - commands as if they were being run by - the OpenEmbedded build system itself. - As noted earlier, the working directory also automatically changes to the - Source Directory (S). - - - - To manually run a specific task using devpyshell, - run the corresponding run.* script in - the - ${WORKDIR}/temp - 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: - - $ bitbake -c task - - Notes - - Execution of a task's run.* - script and BitBake's execution of a task are identical. - In other words, running the script re-runs the task - just as it would be run using the - bitbake -c command. - - Any run.* file that does not - have a .pid extension is a - symbolic link (symlink) to the most recent version of that - file. - - - - - - - Remember, that the devpyshell is a mechanism that allows - you to get into the BitBake task execution environment - through an interactive Python interpreter. - And as such, all commands must be called just as BitBake would call them. - That means you need to provide the appropriate options for - cross-compilation and so forth as applicable. - - - - When you are finished using devpyshell, exit the shell - or close the terminal window. - - - Notes - - - It is worth remembering that when using devpyshell - you need to use the full compiler name such as arm-poky-linux-gnueabi-gcc - instead of just using gcc. - The same applies to other applications such as binutils, - libtool and so forth. - BitBake sets up environment variables such as CC - to assist applications, such as make to find the correct tools. - - - It is also worth noting that devpyshell still works over - X11 forwarding and similar situations. - - -