MIRRORS/poky
1
0
Fork 0
mirror of git://git.yoctoproject.org/poky.git synced 2025-07-19 21:09:03 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

dev-manual/devtool: remove reference to the extensible SDK

Browse Source 
There were leftover references to the extensible SDK after moving the
devtool documentation from the Extensible SDK document to its own
devtool document.

This patch follows the bulk move to make it clear what was modified in
the document.

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
(From yocto-docs rev: 032d2f3297ff4b5ee4e000b3dd0748a58b5f32e0)

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Antonin Godard 2025-01-27 10:58:23 +01:00 committed by Richard Purdie
parent cfe5da1f75
commit 6fd46f2e87
1 changed files with 5 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
documentation/dev-manual/devtool.rst
View File

@ -1046,7 +1046,8 @@ mind:
- The environment in which Make runs is set up with various standard
variables for compilation (e.g. :term:`CC`, :term:`CXX`, and so forth) in a
similar manner to the environment set up by the SDK's environment
similar manner to the environment set up by an :ref:`SDK
<overview-manual/concepts:Application Development SDK>`'s environment
setup script. One easy way to see these variables is to run the
``devtool build`` command on the recipe and then look in
``oe-logs/run.do_compile``. Towards the top of this file, there is
@ -1132,9 +1133,6 @@ these behaviors ensure the reproducibility and integrity of the build.
``devtool add`` does not receive the other parts, which results in
several "command not found" errors.
- In order to support adding Node.js modules, a ``nodejs`` recipe
must be part of your SDK.
As mentioned earlier, you can also add Node.js modules directly from a
repository or local source tree. To add modules this way, use
``devtool add`` in the following form::
@ -1242,10 +1240,8 @@ Recipes often need to use files provided by other recipes on the
:term:`Build Host`. For example,
an application linking to a common library needs access to the library
itself and its associated headers. The way this access is accomplished
within the extensible SDK is through the sysroot. There is one sysroot per
"machine" for which the SDK is being built. In practical terms, this
means there is a sysroot for the target machine, and a sysroot for
the build host.
is through the :term:`Sysroot`. There is a sysroot for the target machine, and a
sysroot for the build host.
Recipes should never write files directly into the sysroot. Instead,
files should be installed into standard locations during the
@ -1259,8 +1255,7 @@ remain free from stale files.
Packaging
---------
Packaging is not always particularly relevant within the extensible SDK.
However, if you examine how build output gets into the final image on
If you examine how build output gets into the final image on
the target device, it is important to understand packaging because the
contents of the image are expressed in terms of packages and not
recipes.