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>

documentation/sdk-manual/sdk-appendix-obtain.rst

@@ -233,6 +233,10 @@ The following figure shows the resulting directory structure after you
 install the Standard SDK by running the ``*.sh`` SDK installation
 script:
 
+.. image:: figures/sdk-installed-standard-sdk-directory.png
+   :scale: 80%
+   :align: center
+
 The installed SDK consists of an environment setup script for the SDK, a
 configuration file for the target, a version file for the target, and
 the root filesystem (``sysroots``) needed to develop objects for the
@@ -255,6 +259,10 @@ The following figure shows the resulting directory structure after you
 install the Extensible SDK by running the ``*.sh`` SDK installation
 script:
 
+.. image:: figures/sdk-installed-extensible-sdk-directory.png
+   :scale: 80%
+   :align: center
+
 The installed directory structure for the extensible SDK is quite
 different than the installed structure for the standard SDK. The
 extensible SDK does not separate host and target parts in the same

documentation/sdk-manual/sdk-extensible.rst

@@ -226,6 +226,9 @@ with ``devtool add`` form different combinations. The following diagram
 shows common development flows you would use with the ``devtool add``
 command:
 
+.. image:: figures/sdk-devtool-add-flow.png
+   :align: center
+
 1. *Generating the New Recipe*: The top part of the flow shows three
    scenarios by which you could use ``devtool add`` to generate a recipe
    based on existing source code.
@@ -372,6 +375,9 @@ with ``devtool modify`` form different combinations. The following
 diagram shows common development flows for the ``devtool modify``
 command:
 
+.. image:: figures/sdk-devtool-modify-flow.png
+   :align: center
+
 1. *Preparing to Modify the Code*: The top part of the flow shows three
    scenarios by which you could use ``devtool modify`` to prepare to
    work on source files. Each scenario assumes the following:
@@ -576,6 +582,9 @@ and work with any source file forms that the
 The following diagram shows the common development flow used with the
 ``devtool upgrade`` command:
 
+.. image:: figures/sdk-devtool-upgrade-flow.png
+   :align: center
+
 1. *Initiate the Upgrade*: The top part of the flow shows the typical
    scenario by which you use the ``devtool upgrade`` command. The
    following conditions exist:

documentation/sdk-manual/sdk-intro.rst

@@ -163,8 +163,12 @@ available a number of different ways:
 SDK Development Model
 =====================
 
-Fundamentally, the SDK fits into the development process as follows: The
-SDK is installed on any machine and can be used to develop applications,
+Fundamentally, the SDK fits into the development process as follows:
+
+.. image:: figures/sdk-environment.png
+   :align: center
+
+The SDK is installed on any machine and can be used to develop applications,
 images, and kernels. An SDK can even be used by a QA Engineer or Release
 Engineer. The fundamental concept is that the machine that has the SDK
 installed does not have to be associated with the machine that has the

documentation/sdk-manual/sdk-working-projects.rst

@@ -18,6 +18,9 @@ workflow, which is outside of the :term:`OpenEmbedded Build System`.
 
 The following figure presents a simple Autotools workflow.
 
+.. image:: figures/sdk-autotools-flow.png
+   :align: center
+
 Follow these steps to create a simple Autotools-based "Hello World"
 project:
 
@@ -128,6 +131,9 @@ This section presents a simple Makefile development flow and provides an
 example that lets you see how you can use cross-toolchain environment
 variables and Makefile variables during development.
 
+.. image:: figures/sdk-makefile-flow.png
+   :align: center
+
 The main point of this section is to explain the following three cases
 regarding variable behavior: