mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-07 16:59:22 +00:00
Code Issues Projects Releases Wiki Activity

manuals: rename "devpyshell" to "pydevshell"

Browse Source 
This addresses [YOCTO #14531] after the "devpyshell" task was renamed
to "pydevshell" in OE core.

(From yocto-docs rev: 1056320e90545c8dff0fc71a5fde752295d4d6e4)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Michael Opdenacker
2021-10-18 17:05:33 +02:00
committed by Richard Purdie
parent 5550d83ff7
commit 07108739ce
2 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/dev-manual/common-tasks.rst
+6 -6
View File
@@ -3531,14 +3531,14 @@ terminal window.
- It is also worth noting that ``devshell`` still works over X11
forwarding and similar situations.
Using a Development Python Shell
Using a Python Development Shell
================================
Similar to working within a development shell as described in the
previous section, you can also spawn and work within an interactive
Python development shell. When debugging certain commands or even when
just editing packages, ``devpyshell`` can be a useful tool. When you
invoke the ``devpyshell`` task, all tasks up to and including
just editing packages, ``pydevshell`` can be a useful tool. When you
invoke the ``pydevshell`` task, all tasks up to and including
:ref:`ref-tasks-patch` are run for the
specified target. Then a new terminal is opened. Additionally, key
Python objects and code are available in the same way they are to
@@ -3563,17 +3563,17 @@ system were executing them. Consequently, working this way can be
helpful when debugging a build or preparing software to be used with the
OpenEmbedded build system.
Following is an example that uses ``devpyshell`` on a target named
Following is an example that uses ``pydevshell`` on a target named
``matchbox-desktop``::
$ bitbake matchbox-desktop -c devpyshell
$ bitbake matchbox-desktop -c pydevshell
This command spawns a terminal and places you in an interactive Python
interpreter within the OpenEmbedded build environment. The
:term:`OE_TERMINAL` variable
controls what type of shell is opened.
When you are finished using ``devpyshell``, you can exit the shell
When you are finished using ``pydevshell``, you can exit the shell
either by using Ctrl+d or closing the terminal window.
Building
documentation/ref-manual/tasks.rst
+4 -4
View File
@@ -516,17 +516,17 @@ scratch is guaranteed.
$ bitbake -f -c do_cleansstate target
.. _ref-tasks-devpyshell:
.. _ref-tasks-pydevshell:
``do_devpyshell``
``do_pydevshell``
-----------------
Starts a shell in which an interactive Python interpreter allows you to
interact with the BitBake build environment. From within this shell, you
can directly examine and set bits from the data store and execute
functions as if within the BitBake environment. See the ":ref:`dev-manual/common-tasks:using a development python shell`" section in
functions as if within the BitBake environment. See the ":ref:`dev-manual/common-tasks:using a python development shell`" section in
the Yocto Project Development Tasks Manual for more information about
using ``devpyshell``.
using ``pydevshell``.
.. _ref-tasks-devshell: