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>

1 files changed, 9 insertions, 0 deletions

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
 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: