doc: update build-from-source instructions

Users no longer need to explicitly generate configuration source code as
they are now generated at build time. This patch updates the relevant
instructions in the documentation.

v3:
 * RELEASE now defaults to n.
 * Cleanup the unnecessary target `all` in the `make` commands
 * Remove menuconfig related stuff.
 * Refine the introductory paragraph as only steps on Ubuntu is introduced
 * Also introduce the targets introduced by PR #5791

v2:
 * Add python3 lxml as a dependency
 * Explain how to use out-of-tree XML files

Tracked-On: #5644
Signed-off-by: Junjie Mao <junjie.mao@intel.com>
Co-authored-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com>

doc/tutorials/acrn_configuration_tool.rst

@@ -191,32 +191,6 @@ current scenario has:
 Configuration Tool Workflow
 ***************************
 
-Hypervisor Configuration Workflow
-==================================
-
-The hypervisor configuration is based on the ``Kconfig``
-mechanism. Begin by creating a board-specific ``defconfig`` file to
-set up the default ``Kconfig`` values for the specified board.
-Next, configure the hypervisor build options using the ``make menuconfig``
-graphical interface or ``make defconfig`` to generate
-a ``.config`` file. The resulting ``.config`` file is
-used by the ACRN build process to create a configured scenario- and
-board-specific hypervisor image.
-
-.. figure:: images/sample_of_defconfig.png
-   :align: center
-
-   defconfig file sample
-
-.. figure:: images/GUI_of_menuconfig.png
-   :align: center
-
-   ``menuconfig`` interface sample
-
-Refer to :ref:`getting-started-hypervisor-configuration` for detailed
-configuration steps.
-
-
 .. _vm_config_workflow:
 
 Board and VM Configuration Workflow
@@ -258,37 +232,8 @@ Here is the offline configuration tool workflow:
    .. note:: Refer to :ref:`acrn_config_tool_ui` for more details on
       the configuration tool UI.
 
-#. Auto generate the code.
-
-   Python tools are used to generate configurations in patch format.
-   The patches are applied to your local ``acrn-hypervisor`` git tree
-   automatically.
-
-   a. Generate a patch for the board-related configuration::
-
-         cd misc/acrn-config/board_config
-         python3 board_cfg_gen.py --board $(BOARD).xml --scenario $(SCENARIO).xml
-
-      Note that this can also be done by clicking **Generate Board SRC** in the acrn-config UI.
-
-
-   #. Generate a patch for scenario-based VM configuration::
-
-         cd misc/acrn-config/scenario_config
-         python3 scenario_cfg_gen.py --board $(BOARD).xml --scenario $(SCENARIO).xml
-
-      Note that this can also be done by clicking **Generate Scenario SRC** in the acrn-config UI.
-
-   #. Generate the launch script for the specified
-      post-launched User VM::
-
-         cd misc/acrn-config/launch_config
-         python3 launch_cfg_gen.py --board $(BOARD).xml --scenario $(SCENARIO).xml --launch $(LAUNCH).xml --uosid xx
-
-      Note that this can also be done by clicking **Generate Launch Script** in the acrn-config UI.
-
-#. Re-build the ACRN hypervisor. Refer to
-   :ref:`getting-started-building` to re-build the ACRN hypervisor on the host machine.
+#. Build with your XML files. Refer to :ref:`getting-started-building` to build
+   the ACRN hypervisor with your XML files on the host machine.
 
 #. Deploy VMs and run ACRN hypervisor on the target board.
 

doc/tutorials/enable_ivshmem.rst

@@ -178,7 +178,7 @@ Linux-based VMs (VM0 is a pre-launched VM and VM2 is a post-launched VM).
    and shared memory size is 2M bytes:
 
    - Edit XML configuration file for hybrid_rt scenario on whl-ipc-i5 board
-     ``acrn-hypervisor/misc/vm_configs/xmls/config-xmls/whl-ipc-i5/hybrid_rt.xml``
+     ``acrn-hypervisor/misc/config_tools/data/whl-ipc-i5/hybrid_rt.xml``
      to enable ``ivshmem`` and configure the shared memory region using the format
      ``shm_name, shm_size, VM IDs`` (as described above in the ACRN dm boot parameters).
      The region name must start with ``hv:/`` for an hv-land shared region, and we'll allocate 2MB
@@ -194,8 +194,7 @@ Linux-based VMs (VM0 is a pre-launched VM and VM2 is a post-launched VM).
 
 2. Build ACRN based on the XML configuration for hybrid_rt scenario on whl-ipc-i5 board::
 
-	make BOARD_FILE=acrn-hypervisor/misc/vm_configs/xmls/board-xmls/whl-ipc-i5.xml \
-	SCENARIO_FILE=acrn-hypervisor/misc/vm_configs/xmls/config-xmls/whl-ipc-i5/hybrid_rt.xml TARGET_DIR=xxx
+	make BOARD=whl-ipc-i5 SCENARIO=hybrid_rt TARGET_DIR=xxx
 
 3. Add a new virtual PCI device for VM2 (post-launched VM): the device type is
    ``ivshmem``, shared memory name is ``hv:/shm_region_0``, and shared memory

doc/tutorials/vuart_configuration.rst

@@ -267,7 +267,7 @@ and :ref:`How to Configure a Communication Port
 <how-to-configure-a-communication-port>`.
 
 You can configure both Legacy vUART and PCI-vUART in
-``./misc/vm_configs/xmls/config-xmls/<board>/<scenario>.xml``. For
+``./misc/config_tools/data/<board>/<scenario>.xml``. For
 example, if VM0 has a legacy vUART0 and a PCI-vUART1, VM1 has no legacy
 vUART but has a PCI-vUART0 and a PCI-vUART1, VM0's PCI-vUART1 and VM1's
 PCI-vUART1 are connected to each other. You  should configure then like this:
@@ -334,13 +334,12 @@ The ACRN vUART related XML fields:
 
 Run the command to build ACRN with this XML configuration file::
 
-  make BOARD_FILE=$PWD/misc/acrn-config/xmls/board-xmls/<board>.xml \
-     SCENARIO_FILE=$PWD/misc/acrn-config/xmls/config-xmls/<board>/<scenario>.xml
+  make BOARD=<board> SCENARIO=<scenario>
 
 The configuration tools will test your settings, and check :ref:`vUART
 Rules <index-of-vuart>` for compilation issue. After compiling, you can find
-``./misc/vm_configs/scenarios/<scenario>/<board>/pci_dev.c`` has been
-changed by the configuration tools based on the XML settings, something like:
+the generated sources under ``build/configs/scenarios/<scenario>/pci_dev.c``
+which is based on the XML settings, something like:
 
 .. code-block:: none