diff --git a/overview/images/qa_executablebuildmanagedc-v4.png b/overview/images/qa_executablebuildmanagedc-v4.png new file mode 100644 index 000000000..fa2d319c0 Binary files /dev/null and b/overview/images/qa_executablebuildmanagedc-v4.png differ diff --git a/overview/images/qa_resources-v4.png b/overview/images/qa_resources-v4.png index 08c45e75d..19a79e793 100644 Binary files a/overview/images/qa_resources-v4.png and b/overview/images/qa_resources-v4.png differ diff --git a/overview/images/qa_resources-v4.pptx b/overview/images/qa_resources-v4.pptx index f8958ff23..4db38505f 100644 Binary files a/overview/images/qa_resources-v4.pptx and b/overview/images/qa_resources-v4.pptx differ diff --git a/overview/index.rst b/overview/index.rst index 3b390e63b..db3b39ae9 100644 --- a/overview/index.rst +++ b/overview/index.rst @@ -92,13 +92,14 @@ The following diagram outlines the SDK content. Please refer to the :ref:`sdk_6_ .. _executableBuildWorkflow: -Build Workflow --------------- +Executable Build Workflow +------------------------- An Executable is built from several input resources and tools. Each component has dependencies and requirements that must be carefully respected in order to build an Executable. + Resources and Dependencies Flow ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -113,7 +114,7 @@ Let's take a closer look at the resources MicroEJ has to offer and where to find VEE Port Build Flow ^^^^^^^^^^^^^^^^^^^ - + To build an application, a VEE Port is required, you can see below how a VEE port is built from a MICROEJ Architecture. .. figure:: images/qa_veeportbuild-v4.png @@ -128,13 +129,13 @@ Executable Build Flow Using a VEE Port here is how we build the executable for embedded devices. -.. figure:: images/qa_executablebuild-v4.png +.. figure:: images/qa_executablebuildmanagedc-v4.png :alt: Executable Build Flow :scale: 70 :align: center Executable Build Flow - + .. | Copyright 2008-2025, MicroEJ Corp. Content in this space is free for read and redistribute. Except if otherwise stated, modification