summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorNicolas Dechesne <nicolas.dechesne@linaro.org>2020-07-29 11:44:03 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-09-17 10:09:34 +0100
commite6c9507240ffd3369196b11193f3b8a0ad4c3b65 (patch)
tree1f8706774b7c8a0723533ed9527d413ce617c81d /documentation
parentc7ff908b50eb12eef0d3da94ae1ee8a3b34ad4c1 (diff)
downloadpoky-e6c9507240ffd3369196b11193f3b8a0ad4c3b65.tar.gz
sphinx: sdk-manual: add figures
(From yocto-docs rev: 33f46470d53790ae986294e1776c5ca23f764976) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/sdk-manual/sdk-appendix-obtain.rst8
-rw-r--r--documentation/sdk-manual/sdk-extensible.rst9
-rw-r--r--documentation/sdk-manual/sdk-intro.rst8
-rw-r--r--documentation/sdk-manual/sdk-working-projects.rst6
4 files changed, 29 insertions, 2 deletions
diff --git a/documentation/sdk-manual/sdk-appendix-obtain.rst b/documentation/sdk-manual/sdk-appendix-obtain.rst
index 015506de01..d6d534ea93 100644
--- a/documentation/sdk-manual/sdk-appendix-obtain.rst
+++ b/documentation/sdk-manual/sdk-appendix-obtain.rst
@@ -233,6 +233,10 @@ The following figure shows the resulting directory structure after you
233install the Standard SDK by running the ``*.sh`` SDK installation 233install the Standard SDK by running the ``*.sh`` SDK installation
234script: 234script:
235 235
236.. image:: figures/sdk-installed-standard-sdk-directory.png
237 :scale: 80%
238 :align: center
239
236The installed SDK consists of an environment setup script for the SDK, a 240The installed SDK consists of an environment setup script for the SDK, a
237configuration file for the target, a version file for the target, and 241configuration file for the target, a version file for the target, and
238the root filesystem (``sysroots``) needed to develop objects for the 242the root filesystem (``sysroots``) needed to develop objects for the
@@ -255,6 +259,10 @@ The following figure shows the resulting directory structure after you
255install the Extensible SDK by running the ``*.sh`` SDK installation 259install the Extensible SDK by running the ``*.sh`` SDK installation
256script: 260script:
257 261
262.. image:: figures/sdk-installed-extensible-sdk-directory.png
263 :scale: 80%
264 :align: center
265
258The installed directory structure for the extensible SDK is quite 266The installed directory structure for the extensible SDK is quite
259different than the installed structure for the standard SDK. The 267different than the installed structure for the standard SDK. The
260extensible SDK does not separate host and target parts in the same 268extensible SDK does not separate host and target parts in the same
diff --git a/documentation/sdk-manual/sdk-extensible.rst b/documentation/sdk-manual/sdk-extensible.rst
index 3df2174fd9..2652b4acd4 100644
--- a/documentation/sdk-manual/sdk-extensible.rst
+++ b/documentation/sdk-manual/sdk-extensible.rst
@@ -226,6 +226,9 @@ with ``devtool add`` form different combinations. The following diagram
226shows common development flows you would use with the ``devtool add`` 226shows common development flows you would use with the ``devtool add``
227command: 227command:
228 228
229.. image:: figures/sdk-devtool-add-flow.png
230 :align: center
231
2291. *Generating the New Recipe*: The top part of the flow shows three 2321. *Generating the New Recipe*: The top part of the flow shows three
230 scenarios by which you could use ``devtool add`` to generate a recipe 233 scenarios by which you could use ``devtool add`` to generate a recipe
231 based on existing source code. 234 based on existing source code.
@@ -372,6 +375,9 @@ with ``devtool modify`` form different combinations. The following
372diagram shows common development flows for the ``devtool modify`` 375diagram shows common development flows for the ``devtool modify``
373command: 376command:
374 377
378.. image:: figures/sdk-devtool-modify-flow.png
379 :align: center
380
3751. *Preparing to Modify the Code*: The top part of the flow shows three 3811. *Preparing to Modify the Code*: The top part of the flow shows three
376 scenarios by which you could use ``devtool modify`` to prepare to 382 scenarios by which you could use ``devtool modify`` to prepare to
377 work on source files. Each scenario assumes the following: 383 work on source files. Each scenario assumes the following:
@@ -576,6 +582,9 @@ and work with any source file forms that the
576The following diagram shows the common development flow used with the 582The following diagram shows the common development flow used with the
577``devtool upgrade`` command: 583``devtool upgrade`` command:
578 584
585.. image:: figures/sdk-devtool-upgrade-flow.png
586 :align: center
587
5791. *Initiate the Upgrade*: The top part of the flow shows the typical 5881. *Initiate the Upgrade*: The top part of the flow shows the typical
580 scenario by which you use the ``devtool upgrade`` command. The 589 scenario by which you use the ``devtool upgrade`` command. The
581 following conditions exist: 590 following conditions exist:
diff --git a/documentation/sdk-manual/sdk-intro.rst b/documentation/sdk-manual/sdk-intro.rst
index 88238d7dd4..215889f390 100644
--- a/documentation/sdk-manual/sdk-intro.rst
+++ b/documentation/sdk-manual/sdk-intro.rst
@@ -163,8 +163,12 @@ available a number of different ways:
163SDK Development Model 163SDK Development Model
164===================== 164=====================
165 165
166Fundamentally, the SDK fits into the development process as follows: The 166Fundamentally, the SDK fits into the development process as follows:
167SDK is installed on any machine and can be used to develop applications, 167
168.. image:: figures/sdk-environment.png
169 :align: center
170
171The SDK is installed on any machine and can be used to develop applications,
168images, and kernels. An SDK can even be used by a QA Engineer or Release 172images, and kernels. An SDK can even be used by a QA Engineer or Release
169Engineer. The fundamental concept is that the machine that has the SDK 173Engineer. The fundamental concept is that the machine that has the SDK
170installed does not have to be associated with the machine that has the 174installed does not have to be associated with the machine that has the
diff --git a/documentation/sdk-manual/sdk-working-projects.rst b/documentation/sdk-manual/sdk-working-projects.rst
index d18568d60a..df216175c9 100644
--- a/documentation/sdk-manual/sdk-working-projects.rst
+++ b/documentation/sdk-manual/sdk-working-projects.rst
@@ -18,6 +18,9 @@ workflow, which is outside of the :term:`OpenEmbedded Build System`.
18 18
19The following figure presents a simple Autotools workflow. 19The following figure presents a simple Autotools workflow.
20 20
21.. image:: figures/sdk-autotools-flow.png
22 :align: center
23
21Follow these steps to create a simple Autotools-based "Hello World" 24Follow these steps to create a simple Autotools-based "Hello World"
22project: 25project:
23 26
@@ -128,6 +131,9 @@ This section presents a simple Makefile development flow and provides an
128example that lets you see how you can use cross-toolchain environment 131example that lets you see how you can use cross-toolchain environment
129variables and Makefile variables during development. 132variables and Makefile variables during development.
130 133
134.. image:: figures/sdk-makefile-flow.png
135 :align: center
136
131The main point of this section is to explain the following three cases 137The main point of this section is to explain the following three cases
132regarding variable behavior: 138regarding variable behavior:
133 139