[edk2-wiki][PATCH v1 1/4] Add initial How to Build with Stuart Document

["Michael Kubacki" <mikuback@linux.microsoft.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 28486 bytes --]

From: Michael Kubacki <michael.kubacki@microsoft.com>

Adds a new document that comprehensively describes how to manually
set up a build environment using Stuart.

Covers the following topics:

1. Pre-requisites - Git, Python, compilers, SDKs, etc.
2. Initial steps - Cloning the repo, set up Python virtual env, etc.
3. Stuart command explanation and corresponding examples
4. Common developer scenarios with examples showing what to do
5. Common questions section with answers

Stuart presents a relatively consistent interface to build most
content in edk2 so this document is meant as a long-term starting
point for new contributors to understand the basics of using Stuart
for various areas they are working in within edk2.

Cc: Sean Brogan <sean.brogan@microsoft.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
---
 How-to-Build-With-Stuart.md | 720 ++++++++++++++++++++
 1 file changed, 720 insertions(+)

diff --git a/How-to-Build-With-Stuart.md b/How-to-Build-With-Stuart.md
new file mode 100644
index 000000000000..c8a13a576fec
--- /dev/null
+++ b/How-to-Build-With-Stuart.md
@@ -0,0 +1,720 @@
+# How to Build in edk2 with Stuart
+
+EDK II packages are easy to build with set of tools called "stuart".
+
+>💡 If you are familiar with the `build` command and would like to learn about `build` vs `stuart`,
+>   [click here](Build-Instructions.md#build-option-comparison).
+
+Steps are split into two categories: [(1) one-time](#one-time-steps) and [(2) regular use](#regular-use-steps).
+
+## One-Time Steps
+
+If you've already completed these steps you don't need to run them again.
+
+<details>
+  <summary>Pre-requisites (Git, Python, Compiler)</summary>
+  <hr>
+
+  <ul>
+  <li>
+  <strong>Git - Source Control Management (SCM) Tool</strong>
+
+  Git is the source control management tool used by this project.
+
+  You need <code>git</code> to pull the edk2 source code onto your system, make changes in the code, and submit
+  your changes back to the GitHub repository.
+
+  <a href="https://git-scm.com/downloads" target="_blank">Git Download Page</a>
+  </li>
+  <li>
+  <strong>Python</strong>
+
+  Python is a programming language that many of the edk2 build tools are written in.
+
+  You will need Python to run the edk2 build tools including <code>stuart</code>, which is written in Python.
+
+  It is recommended you install a Python version that is equal to the version used in the
+  <code>UsePythonVersion@0</code> step in this file
+  <a href="https://github.com/tianocore/edk2/blob/master/.azurepipelines/templates/pr-gate-steps.yml" target="_blank">.azurepipelines/templates/pr-gate-steps.yml</a>.
+
+  That version is constantly tested against the code in the repository.
+
+  <a href="https://www.python.org/downloads/" target="_blank">Python Download Page</a>
+  </li>
+  <li>
+  <strong>C Compiler</strong>
+
+  A C compiler is needed to compile the firmware code.
+
+  Several options are available. This is an area where direct guidance cannot be provided.
+
+  You will need to choose a compiler supported on your host operating system and the particular firmware packages
+  you are building.
+
+  However, it is common to use:
+  <ul>
+    <li><a href="https://gcc.gnu.org/" target="_blank">GCC</a> on Linux</li>
+    <details>
+      <summary>Ubuntu GCC Installation Instructions</summary>
+      <code>apt-get update && apt-get install -y build-essential git nasm wget m4 bison flex uuid-dev python unzip acpica-tools gcc-multilib</code>
+    </details>
+    <li><a href="https://visualstudio.microsoft.com/downloads/" target="_blank">Visual Studio</a> on Windows</li>
+    <details>
+      <summary>Visual Studio Installation Instructions (Windows)</summary>
+      <br>
+      <details>
+        <summary>Visual Studio 2022 Installation Instructions</summary>
+        <hr>
+        <p>
+          Click to download <a href="https://aka.ms/vs/17/release/vs_BuildTools.exe" target="_blank">Visual Studio 2022 Build Tools</a>
+        </p>
+        <ol>
+          <li>
+            Open an <strong>Administrator Command Prompt</strong> by right-clicking on <strong>Command Prompt</strong> and
+            select <strong>Run as Administrator</strong>
+          </li>
+          <li>
+            Change to the directory where you downloaded the <code>vs_BuildTools.exe</code> file
+            (e.g. <code>C:\Downloads</code>)
+          </li>
+          <li>
+            Enter the following command:
+            <br>
+            <kbd>
+              start /w vs_BuildTools.exe --quiet --wait --norestart --nocache --installPath C:\BuildTools ^
+              --add Microsoft.VisualStudio.Component.VC.CoreBuildTools --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 ^
+              --add Microsoft.VisualStudio.Component.Windows11SDK.22000 --add Microsoft.VisualStudio.Component.VC.Tools.ARM ^
+              --add Microsoft.VisualStudio.Component.VC.Tools.ARM64
+            </kbd>
+          </li>
+        </ol>
+        <hr>
+    </details>
+    <details>
+      <summary>Visual Studio 2019 Installation Instructions</summary>
+      <hr>
+      <p>
+        Click to download <a href="https://aka.ms/vs/16/release/vs_BuildTools.exe" target="_blank">Visual Studio 2019 Build Tools</a>
+      </p>
+      <ol>
+        <li>
+          Open an <strong>Administrator Command Prompt</strong> by right-clicking on <strong>Command Prompt</strong> and
+          select <strong>Run as Administrator</strong>
+        </li>
+        <li>
+          Change to the directory where you downloaded the <code>vs_BuildTools.exe</code> file
+          (e.g. <code>C:\Downloads</code>)
+        </li>
+        <li>
+          Enter the following command:
+          <br>
+          <kbd>
+            start /w vs_BuildTools.exe --quiet --wait --norestart --nocache --installPath C:\BuildTools ^
+            --add Microsoft.VisualStudio.Component.VC.CoreBuildTools --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 ^
+            --add Microsoft.VisualStudio.Component.Windows10SDK.19041 --add Microsoft.VisualStudio.Component.VC.Tools.ARM ^
+            --add Microsoft.VisualStudio.Component.VC.Tools.ARM64
+          </kbd>
+        </li>
+      </ol>
+      <hr>
+    </details>
+    <details>
+      <summary>Visual Studio 2017 Installation Instructions</summary>
+      <hr>
+      <p>
+        Click to download <a href="https://aka.ms/vs/15/release/vs_BuildTools.exe" target="_blank">Visual Studio 2017 Build Tools</a>
+      </p>
+      <ol>
+        <li>
+        Open an <strong>Administrator Command Prompt</strong> by right-clicking on <strong>Command Prompt</strong> and
+        select <strong>Run as Administrator</strong>
+        </li>
+        <li>
+        Change to the directory where you downloaded the <code>vs_BuildTools.exe</code> file
+        (e.g. <code>C:\Downloads</code>)
+        </li>
+        <li>
+          Enter the following command:
+          <br>
+          <kbd>
+            start /w vs_BuildTools.exe --quiet --wait --norestart --nocache --installPath C:\BuildTools ^
+            --add Microsoft.VisualStudio.Component.VC.CoreBuildTools --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 ^
+            --add Microsoft.VisualStudio.Component.Windows10SDK.17763 --add Microsoft.VisualStudio.Component.VC.Tools.ARM ^
+            --add Microsoft.VisualStudio.Component.VC.Tools.ARM64
+          </kbd>
+        </li>
+      </ol>
+      <hr>
+    </details>
+    <p>
+      <ul>
+        <li>
+          Note: You can find the latest version of Visual Studio supported by edk2 on the
+          <a href="https://github.com/tianocore/edk2#core-ci-build-status" target="_blank">CI Status</a> section of the repo readme file.
+        </li>
+        <li>
+          Note: If you still run into build problems finding tools in the SDK, try installing the Windows SDK manually
+          using the following instructions.
+        </li>
+      </ul>
+    </p>
+    <details>
+      <summary>Optional: Install the Windows SDK manually</summary>
+      <hr>
+      <p>
+        Download the Windows Software Development Kit (SDK) from
+        <a href="https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/" target="_blank">Windows Dev Center - Windows SDK</a>
+      </p>
+      <p>
+        Follow the default options until you reach the "<strong>Select the features you want to install</strong>" page.
+      </p>
+      Select the following options:
+      <ul>
+        <li>Windows SDK Signing Tools for Desktop Apps</li>
+        <li>Windows SDK for UWP Managed Apps</li>
+        <li>Windows SDK for UWP C++ Apps</li>
+        <li>Windows SDK for Desktop C++ x86 Apps</li>
+        <li>Windows SDK for Desktop C++ amd64 Apps</li>
+        <li>Windows SDK for Desktop C++ arm Apps</li>
+      </ul>
+      <p>
+        Click <strong>Download</strong> and complete the installation process.
+      </p>
+      <hr>
+    </details>
+  </ul>
+  </li>
+  </ul>
+  <hr>
+</details>
+
+1. Clone the edk2 repo
+   - Open a command-prompt in the directory where you would like to keep the edk2 repo
+   - Clone the repo
+     - Example: `git clone edk2`
+
+2. Change into the edk2 directory
+   - `cd edk`
+
+3. Create a Python virtual environment
+    - Note that the steps differ between Linux and Windows.
+      - <details>
+        <summary>Linux Instructions</summary>
+        <code>python -m venv .venv</code>
+        <br>
+        <code>source .venv/bin/activate</code>
+        </details>
+      - <details>
+        <summary>Windows Instructions</summary>
+        <code>py -m venv .venv</code>
+        <br>
+        <code>.venv\Scripts\activate.bat</code>
+        </details>
+
+4. Tell Git to ignore the Python virtual environment
+
+    The problem: Git will try to track your Python virtual environment as new code changes if it is not told to
+    ignore it.
+
+    - Open the file `.git/info/exclude`
+      - `cd .git`
+      - `cd info`
+      - Open the `exclude` file in a text editor
+      - Add the following line to the end of the file:
+        - `*venv*/**`
+      - Close the file
+    - Note: Git will no longer try to track your Python virtual environments in this repository.
+
+That's it!
+
+Your terminal may now indicate that a virtual environment is active by showing `(.venv)` before the
+current line.
+
+## Regular Use Steps
+
+These are steps you should run on a regular basis.
+
+The steps are split into two categories: (1) once per session and (2) before each build.
+
+### Once Per Session Steps
+
+These assume your command prompt is in the edk2 repository directory.
+
+1. Activate the Python virtual environment
+    - Linux
+      - `source .venv/bin/activate`
+    - Windows
+      - `.venv\Scripts\activate.bat`
+
+2. Update Python PIP modules
+     - `pip install -r pip-requirements.txt --upgrade`
+
+3. Get updated code dependencies
+     - `stuart_setup -c .pytool/CISettings.py`
+
+That's it!
+
+Now every time you would like to build the code, you only need to run the following commands until you end this
+session and return.
+
+1. Update other dependencies (like binaries)
+    - `stuart_update -c .pytool/CISettings.py`
+
+2. Run CI build (--help will give you options)
+    - `stuart_ci_build -c .pytool/CISettings.py TOOL_CHAIN_TAG=<your tag here>`
+
+      - Common options:
+        - `-p <pkg1,pkg2,pkg3>`: To build only certain packages use a comma-separated list
+        - `-a <arch1,arch2,arch3>`: To run only certain architectures use a comma-separated list
+        - `-t <target1,target2>`: To run only tests related to certain targets use a comma-separated list
+
+That's it to do a basic build.
+
+The remainder of this page contains more details about the `stuart_ci_build` and `stuart_build` commands.
+
+---
+
+## Examples
+
+<details>
+<summary>Example: I want to build MdeModulePkg to test a change I made there.</summary>
+<hr>
+<p>
+The important parameter here is the <code>-p</code> parameter which specifies that <code>MdeModulePkg</code> should
+be built.
+</p>
+<p>
+The example below uses:
+<ul>
+<li>
+The <code>TOOL_CHAIN_TAG</code> parameter to specify the build should use <code>VS2019</code> (Visual Studio 2019).
+</li>
+<li>
+The <code>-a</code> parameter is used to specify that the <code>IA32</code> and <code>X64</code> architectures should
+be built.
+</li>
+</ul>
+</p>
+
+<kbd>stuart_ci_build -c .pytool/CISettings.py -p MdeModulePkg -a IA32,X64 TOOL_CHAIN_TAG=VS2019</kbd>
+<hr>
+</details>
+
+<details>
+<summary>Example: I want to build OvmfPkg to test a change I made there.</summary>
+<hr>
+<p>
+OvmfPkg is considered a "platform firmware" for the
+<a href="https://www.qemu.org/" target="_blank">QEMU open-source emulator</a>.
+
+<ul>
+<li>
+Therefore, it provides a platform build file (see <a href="#what-is-platformbuild-py">What is PlatformBuild.py?</a>)
+<ul>
+<li>
+Located at <a href="https://github.com/tianocore/edk2/blob/master/OvmfPkg/PlatformCI/PlatformBuild.py" target="_blank">OvmfPkg/PlatformCI/PlatformBuild.py</a>
+</li>
+</ul>
+</li>
+<li>
+Because we are building a platform build file, the build command will be <code>stuart_build</code> instead of
+<code>stuart_ci_build</code> to compile the code
+</li>
+</ul>
+
+<kbd>stuart_build -c PlatformBuild.py -p OvmfPkg -a IA32,X64 TOOL_CHAIN_TAG=VS2019</kbd>
+
+<p>
+If you want to run CI checks such as CI plugins, you can use <code>stuart_ci_build</code> with the CI build file.
+</p>
+
+<kbd>stuart_ci_build -c .pytool/CISettings.py -p OvmfPkg -a IA32,X64 TOOL_CHAIN_TAG=VS2019</kbd>
+
+<hr>
+</details>
+<details>
+
+<summary>Example: I want to build OvmfPkg and automatically run with my firmware after build.</summary>
+<hr>
+<p>
+OvmfPkg is considered a "platform firmware" for the
+<a href="https://www.qemu.org/" target="_blank">QEMU open-source emulator</a>.
+
+<ul>
+<li>
+Therefore, it provides a platform build file (see <a href="#what-is-platformbuild-py">What is PlatformBuild.py?</a>)
+<ul>
+<li>
+Located at <a href="https://github.com/tianocore/edk2/blob/master/OvmfPkg/PlatformCI/PlatformBuild.py" target="_blank">OvmfPkg/PlatformCI/PlatformBuild.py</a>
+</li>
+</ul>
+</li>
+<li>
+Because we are building a platform build file, the build command will be <code>stuart_build</code> instead of
+<code>stuart_ci_build</code>
+</li>
+</ul>
+
+To see what parameters are supported by this platform build file (at the time this page was written), we can pass the
+<code>--help</code> argument to the <code>stuart_build</code> command:
+
+<pre>
+❯ stuart_build -c PlatformBuild.py --help
+usage: stuart_build [-h] [--SKIPBUILD] [--SKIPPREBUILD] [--SKIPPOSTBUILD] [--FLASHONLY] [--FLASHROM]
+                    [--UPDATECONF] [--CLEAN] [--CLEANONLY] [--OUTPUTCONFIG OUTPUTCONFIG] [-a BUILD_ARCH]
+                    [--build-config BUILD_CONFIG] [--verbose]
+
+options:
+  -h, --help            show this help message and exit
+  --SKIPBUILD, --skipbuild, --SkipBuild
+                        Skip the build process
+  --SKIPPREBUILD, --skipprebuild, --SkipPrebuild
+                        Skip prebuild process
+  --SKIPPOSTBUILD, --skippostbuild, --SkipPostBuild
+                        Skip postbuild process
+  --FLASHONLY, --flashonly, --FlashOnly
+                        Flash rom after build.
+  --FLASHROM, --flashrom, --FlashRom
+                        Flash rom. Rom must be built previously.
+  --UPDATECONF, --updateconf, --UpdateConf
+                        Update Conf. Builders Conf files will be replaced with latest template files
+  --CLEAN, --clean, --CLEAN
+                        Clean. Remove all old build artifacts and intermediate files
+  --CLEANONLY, --cleanonly, --CleanOnly
+                        Clean Only. Do clean operation and don't build just exit.
+  --OUTPUTCONFIG OUTPUTCONFIG, --outputconfig OUTPUTCONFIG, --OutputConfig OUTPUTCONFIG
+                        Provide shell variables in a file
+  -a BUILD_ARCH, --arch BUILD_ARCH
+                        Optional - CSV of architecture to build. IA32 will use IA32 for Pei & Dxe. X64 will use
+                        X64 for both PEI and DXE. IA32,X64 will use IA32 for PEI and X64 for DXE. default is
+                        IA32,X64
+  --build-config BUILD_CONFIG
+                        Provide shell variables in a file
+  --verbose, --VERBOSE, -v
+                        verbose
+
+positional arguments:
+  <key>=<value>              - Set an env variable for the pre/post build process
+  BLD_*_<key>=<value>        - Set a build flag for all build types
+                               (key=value will get passed to build process)
+  BLD_<TARGET>_<key>=<value> - Set a build flag for build type of <target>
+                               (key=value will get passed to build process for given build type)
+</pre>
+</p>
+<p>
+The <code>--flashonly</code> and <code>--flashrom</code> commands are especially useful with OvmfPkg. They
+automatically load QEMU with the newly built firmware.
+
+The example below uses:
+<ul>
+<li>The <code>TOOL_CHAIN_TAG</code> parameter to specify that the build should use <code>GCC5</code>
+to build with GCC.
+</li>
+<li>
+The <code>-a</code> parameter is used to specify the <code>IA32</code> and <code>X64</code> architectures should be
+built.
+</li>
+<li>
+The <code>--flashrom</code> parameter is used to load the firmware in QEMU and boot QEMU after the firmware build
+is completed.
+</li>
+</ul>
+</p>
+
+<kbd>stuart_build -c PlatformBuild.py -p OvmfPkg -a IA32,X64 TOOL_CHAIN_TAG=GCC5 --flashrom</kbd>
+<hr>
+</details>
+
+<details>
+<summary>Example: I want to build BaseTools.</summary>
+<hr>
+<a href="#what-are-basetools">BaseTools</a> has its own build script that leverages
+<a href="#what-are-edk2-pytools">edk2-pytools</a> to build the BaseTools applications.
+<br>
+<br>
+<details>
+<summary>Linux (Ubuntu) Pre-Steps</summary>
+<kbd>sudo apt update</kbd>
+<br>
+<kbd>sudo apt install build-essential uuid-dev</kbd>
+</details>
+<p>
+The file <a href="https://github.com/tianocore/edk2/blob/master/BaseTools/Edk2ToolsBuild.py" target="_blank">BaseTools/Edk2ToolsBuild.py</a>
+can be called as a standalone Python script. You just need to pass the tool chain tag you would like to build with.
+
+Example:
+<kbd>python BaseTools/Edk2ToolsBuild.py -t GCC5</kbd>
+</p>
+<hr>
+</details>
+
+<details>
+<summary>Example: I just want to check if my changes will pass all the non-compiler checks in CI.</summary>
+<hr>
+<p>
+The <code>NO-TARGET</code> build target specifies that the actual firmware source code should not be built for any
+particular target and, instead, the other parts of the CI process will be active such as the non-compiler checks
+(<a href="#what-are-plugins">plugins</a>).
+</p>
+<p>
+In the following example, the CI plugins will be run against all packages supported by the
+<a href="#what-is-ci-settings-py">CISettings.py</a> file.
+</p>
+<kbd>stuart_ci_build -c .pytool/CISettings.py -t NO-TARGET</kbd>
+<p>
+The CI checks could be run against a single package (or a selection of packages) by passing the package names to
+with the <code>-p</code> parameter.
+</p>
+<kbd>stuart_ci_build -c .pytool/CISettings.py -p MdePkg,UefiCpuPkg -t NO-TARGET</kbd>
+<hr>
+</details>
+
+<details>
+<summary>Example: I want to fix all the spelling errors in my package. How do I just run the spell
+         check plugin?</summary>
+<hr>
+<p>
+Plugins are automatically discovered in the workspace by stuart.
+</p>
+<p>The easiest way to have stuart only one run plugin if many others are present (as is the case in edk2) is to simply
+delete the other plugin directories so they are not discovered. You can then test with the remaining plugins and then
+use git to restore the deleted plugin directories back when done testing.
+</p>
+<p>
+For example, to only test with the <code>SpellCheck</code> plugin, delete every other plugin folder from
+<a href="https://github.com/tianocore/edk2/tree/master/.pytool/Plugin" target="_blank">.pytool/Plugin</a> in your
+workspace.
+</p>
+<p>
+Run the command to only perform CI checks:
+<br>
+<kbd>stuart_ci_build -c .pytool/CISettings.py -t NO-TARGET</kbd>
+</p>
+<p>
+When done, restore the other plugin directories:
+<br>
+<kbd>git restore .pytool/Plugin/**</kbd>
+</p>
+<hr>
+</details>
+
+## Common Questions
+
+<details>
+<summary id="what-is-ci">What is CI?</summary>
+<hr>
+<p>
+<a href="https://en.wikipedia.org/wiki/Continuous_integration" target="_blank">Continuous Integration</a>
+</p>
+<p>
+Continuous integration is used in edk2 to test new contributions before they are merged to the edk2 main branch. Stuart
+is used within the edk2 CI process to pull build dependencies and build the code.
+
+You can use stuart to perform the same CI checks locally that are done on the server (see the examples section).
+
+Also see <a href="https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Continuous-Integration" target="_blank">EDK II Continuous Integration</a>.
+</p>
+<hr>
+</details>
+
+<details>
+<summary id="what-are-basetools">What are BaseTools?</summary>
+<hr>
+<p>
+A collection of build related tools for edk2.
+</p>
+<p>
+Examples:
+
+<ul>
+<li>AutoGen</li>
+<li>Build</li>
+<li>GenSec</li>
+<li>GenFV</li>
+<li>GenFW</li>
+<li>GenRds</li>
+</ul>
+</p>
+Each tool has a user manual located in <a href="https://github.com/tianocore/edk2/tree/master/BaseTools/UserManuals" target="_blank">BaseTools/UserManuals</a>.
+</p>
+<p>
+A more complete list of BaseTools is located in the <a href="https://github.com/tianocore/edk2/tree/master/BaseTools/UserManuals" target="_blank">EDK II Tools List</a>.
+</p>
+<hr>
+</details>
+
+<details>
+<summary id="what-are-edk2-pytools">What are edk2-pytools?</summary>
+<hr>
+<p>
+A collection of Python code for working with edk2.
+</p>
+<ul>
+<li>
+<a href="https://github.com/tianocore/edk2-pytool-library" target="_blank">edk2-pytool-library</a> - Python library
+code that seeks to provide an easy way to organize and share edk2 related functionality to facilitate reuse across
+environments, tools, and scripts.
+</li>
+<li>
+<a href="https://github.com/tianocore/edk2-pytool-extensions" target="_blank">edk2-pytool-extensions</a> - A Python
+project that consists of command line and other tools and extensions for building and maintaining an edk2 based UEFI
+firmware code tree.
+</li>
+</ul>
+<hr>
+</details>
+
+<details>
+<summary id="what-is-ci-settings-py">What is CISettings.py?</summary>
+<hr>
+<p>
+<code>CISettings.py</code> is a common name given to a configuration file used with Stuart for CI. It is often stored
+in a folder named <code>.pytools</code> in the root of a repository. So you'll likely encounter commands like the
+following be used with the file:
+</p>
+
+<ul>
+<li>
+<kbd>
+stuart_ci_setup -c .pytool/CISettings.py TOOL_CHAIN_TAG=PUT_TAG_VALUE_HERE
+</kbd>
+</li>
+<li>
+<kbd>
+stuart_update -c .pytool/CISettings.py TOOL_CHAIN_TAG=PUT_TAG_VALUE_HERE
+</kbd>
+</li>
+<li>
+<kbd>
+stuart_ci_build -c .pytool/CISettings.py TOOL_CHAIN_TAG=PUT_TAG_VALUE_HERE
+</kbd>
+</li>
+</ul>
+<hr>
+</details>
+
+<details>
+<summary id="what-is-platformbuild-py">What is PlatformBuild.py?</summary>
+<hr>
+<p>
+<code>PlatformBuild.py</code> is a common name given to a configuration file used with Stuart for platform build. It
+is often stored in the root directory of the package it builds.
+</p>
+<p>
+For example:
+</p>
+<ul>
+<li>
+<kbd>
+stuart_setup -c SomePkg/PlatformBuild.py TOOL_CHAIN_TAG=PUT_TAG_VALUE_HERE
+</kbd>
+</li>
+<li>
+<kbd>
+stuart_update -c SomePkg/PlatformBuild.py TOOL_CHAIN_TAG=PUT_TAG_VALUE_HERE
+</kbd>
+</li>
+<li>
+<kbd>
+stuart_build -c SomePkg/PlatformBuild.py TOOL_CHAIN_TAG=PUT_TAG_VALUE_HERE
+</kbd>
+</li>
+</ul>
+<p>
+Like Stuart CI has "CI plugins", the build process has "build plugins". These can hook into the build in "pre-build"
+or "post-build".
+
+<blockquote>
+Note: Build plugins will also run during CI if a CompilerPlugin is present that builds the code.
+</blockquote>
+</p>
+<hr>
+</details>
+
+<details>
+<summary id="stuart-ci-build-vs-stuart-build">What is the difference between <code>stuart_ci_build</code> and <code>stuart_build</code>?</summary>
+<hr>
+<ul>
+<li>
+<code>stuart_ci_build</code> - Runs CI plugins. By default, often runs CI on several packages at once. This includes
+all of the checks needed to consider the code ready for integration to the mainline.
+</li>
+<li>
+<code>stuart_build</code> - Does not run CI plugins. Builds one platform. Platforms often expose platform-specific
+parameters as defined in their <code>PlatformBuild.py</code> file.
+</li>
+</ul>
+<hr>
+</details>
+
+<details>
+<summary id="what-does-stuart-ci-build-do">What does <code>stuart_ci_build</code> do exactly?</summary>
+<hr>
+<p>
+The Stuart CI process is composed of "CI plugins" that get discovered in the code tree at CI time and hook into
+the CI process. Some examples of CI plugins are a host-based unit test compile and execution, spell checking the code,
+performing markdown lint on the code, etc. Firmware (C code) compilation is performed during CI by a compiler CI
+plugin.
+</p>
+<p>
+Each plugin reports back a pass/fail status. If any plugin fails, CI fails. However, plugins usually provide some
+level of customization in a "CI package configuration file". If this file is present, it is in the root of the package
+with the naming convention <code>PkgName.ci.yaml</code>. For example,
+<a href="https://github.com/tianocore/edk2/blob/master/MdePkg/MdePkg.ci.yaml" target="_blank">MdePkg.ci.yaml</a> is
+the CI package configuration file for <code>MdePkg</code>. Sometimes, CI plugins will allow the plugin to be set to
+run in "audit mode" so the plugin will run and report results but not fail CI if errors are found. As an example, some
+packages in edk2 currently use this file to run the spell checker CI plugin in audit mode.
+</p>
+<p>
+The two main places to look for CI settings are:
+<ul>
+<li>The CISettings.py file - Usually has repo-wide CI settings</li>
+<li>The CI package configuration file - Has package-specific CI settings for a given package</li>
+</ul>
+</p>
+<hr>
+</details>
+
+<details>
+<summary id="how-do-i-get-more-detailed-error-info">How do I get more detailed information if an error happens?</summary>
+<hr>
+<p>
+Look in your <code>/Build</code> directory.
+</p>
+<p>
+Each Stuart command produces a separate file. Open the file corresponding to the command you're using that has the
+failure.
+</p>
+<ul>
+<li><code>stuart_ci_setup</code> - <code>CISETUP.txt</code></li>
+<li><code>stuart_setup</code> - <code>SETUPLOG.txt</code></li>
+<li><code>stuart_update</code> - <code>UPDATE_LOG.txt</code></li>
+<li><code>stuart_ci_build</code> - <code>CI_BUILDLOG.txt</code></li>
+<li><code>stuart_build</code> - <code>BUILDLOG_PACKAGENAME.txt</code></li>
+</ul>
+<hr>
+</details>
+
+<details>
+<summary id="what-are-plugins">What are "plugins"?</summary>
+<hr>
+<p>
+The different types of plugins supported by Stuart and details about each type are available in:
+<br>
+<br>
+The
+<a href="https://github.com/tianocore/edk2-pytool-extensions/blob/master/docs/user/features/plugin_manager.md" target="_blank">edk2-pytool-extensions Plugin Manager</a>
+page.
+</p>
+<hr>
+</details>
+
+<details>
+<summary id="how-do-i-get-lower-level-technical-details">How do I get lower-level technical details?</summary>
+<hr>
+<p>
+Start in the
+<a href="https://github.com/tianocore/edk2-pytool-extensions/blob/master/docs/user/index.md" target="_blank">edk2-pytool-extensions User Documentation</a>.
+</p>
+<hr>
+</details>
-- 
2.28.0.windows.1