From fb65c424688eec01c14dc807b468b1b882dec078 Mon Sep 17 00:00:00 2001 From: guoqingxz Date: Sun, 10 May 2020 16:22:33 +0800 Subject: [PATCH] doc: update build ACRN doc Signed-off-by: guoqingxz --- doc/getting-started/building-from-source.rst | 6 +++--- doc/tutorials/building_acrn_in_docker.rst | 9 +-------- 2 files changed, 4 insertions(+), 11 deletions(-) diff --git a/doc/getting-started/building-from-source.rst b/doc/getting-started/building-from-source.rst index 0d4c44c8b..511be8032 100644 --- a/doc/getting-started/building-from-source.rst +++ b/doc/getting-started/building-from-source.rst @@ -267,8 +267,8 @@ The ``acrn.efi`` will be generated in the ``./hypervisor/build/acrn.efi`` direct As mentioned in :ref:`ACRN Configuration Tool `, the Board configuration and VM configuration can be imported from XML files. If you want to build the hypervisor with XML configuration files, -specify the file location as follows (assuming you're current directory -is at the top level of the acrn-hypervisor directory): +specify the file location as follows (assuming you're at the top level +of the acrn-hypervisor directory): .. code-block:: none @@ -281,7 +281,7 @@ is at the top level of the acrn-hypervisor directory): information is retrieved from the corresponding ``BOARD_FILE`` and ``SCENARIO_FILE`` XML configuration files. The ``TARGET_DIR`` parameter specifies what directory is used to store configuration files imported - from XML files. If the ``TARGED_DIR`` it is not specified, the original + from XML files. If the ``TARGED_DIR`` is not specified, the original configuration files of acrn-hypervisor would be overridden. Follow the same instructions to boot and test the images you created from your build. diff --git a/doc/tutorials/building_acrn_in_docker.rst b/doc/tutorials/building_acrn_in_docker.rst index 709959f5e..4a5582425 100644 --- a/doc/tutorials/building_acrn_in_docker.rst +++ b/doc/tutorials/building_acrn_in_docker.rst @@ -49,14 +49,7 @@ Build the Docker Image from Dockerfile Alternatively, you can build your own local Docker image using the provided Dockerfile build instructions by following these steps. You'll -need to this this if you're working behind a corporate proxy. - -.. note:: - A known `issue - `_ exists - while building the ACRN hypervisor. Refer to `Get the Docker Image from - Docker Hub`_ as a temporary way to obtain the Docker Image for the v1.6 - release. +need this if you're working behind a corporate proxy. #. Download `Dockerfile `_ to your development machine.