From: "Agyeman, Prince" <prince.agyeman@intel.com>
To: devel@edk2.groups.io
Cc: chasel.chiu@intel.com, Prince Agyeman <prince.agyeman@intel.com>
Subject: [edk2-platforms] [PATCH v2 5/5] Intel/Readme.md: Updated readme with linux build instructions
Date: Mon, 20 May 2019 20:08:15 -0700 [thread overview]
Message-ID: <3793b1cdad9c68d23ec1378f35f5fef9e4d42ced.1558406058.git.prince.agyeman@intel.com> (raw)
In-Reply-To: <cover.1558406058.git.prince.agyeman@intel.com>
From: Prince Agyeman <prince.agyeman@intel.com>
Signed-off-by: Prince Agyeman <prince.agyeman@intel.com>
---
Platform/Intel/Readme.md | 42 ++++++++++++++++++++++++------------------
1 file changed, 24 insertions(+), 18 deletions(-)
diff --git a/Platform/Intel/Readme.md b/Platform/Intel/Readme.md
index 1da5d0a..443fb40 100644
--- a/Platform/Intel/Readme.md
+++ b/Platform/Intel/Readme.md
@@ -107,9 +107,13 @@ return back to the minimum platform caller.
**Building with the python script**
-1. Open command window, go to the workspace directory, e.g. c:\Kabylake.
-2. Type "cd edk2-platforms\Platform\Intel
-3. Type "python build_bios.py -p REPLACE_WITH_BOARD_NAME"
+1. Open command window, go to the workspace directory, e.g. c:\Kabylake or ~/Kabylake in the case of a linux OS
+2. If using a linux OS
+ * Type "cd edk2"
+ * Type "source edksetup.sh"
+ * Type "cd ../" to go back to the workspace directory
+3. Type "cd edk2-platforms/Platform/Intel
+4. Type "python build_bios.py -p REPLACE_WITH_BOARD_NAME"
* build_bios.py arguments:
@@ -132,18 +136,19 @@ return back to the minimum platform caller.
| |
* For more information on build options
- * ``Type "python build_bios.py -h"``
+ * Type "python build_bios.py -h"
* Note
- * ``Python 2.7.16 and Python 3.7.3 compatible``
- * ``These python build scripts have been tested on Windows due to`` [cross-platform limitations](#Known-limitations)
+ * Python 2.7.16 and Python 3.7.3 compatible
+ * This python build script has been tested on Windows 10 and Ubuntu 16.04.5 LTS
+ * See [cross-platform limitations](#Known-limitations)
* Configuration Files
- * ``The edk2-platforms\Platform\Intel\build.cfg file contains the default settings used by build_bios.py``
- * ``The default settings are under the DEFAULT_CONFIG section``
- * ``Each board can have a settings file that will override the edk2-platforms\Platform\Intel\build.cfg settings``
- * ``An example of a board specific settings:``
- * ``edk2-platforms\Platform\Intel\KabylakeOpenBoardPkg\KabylakeRvp3\build_config.cfg``
+ * The edk2-platforms\Platform\Intel\build.cfg file contains the default settings used by build_bios.py
+ * The default settings are under the DEFAULT_CONFIG section
+ * Each board can have a settings file that will override the edk2-platforms\Platform\Intel\build.cfg settings
+ * An example of a board specific settings:
+ * edk2-platforms\Platform\Intel\KabylakeOpenBoardPkg\KabylakeRvp3\build_config.cfg
* Workspace view of the build scripts
* <pre>
@@ -212,14 +217,13 @@ Users can also flash the UEFI firmware image to the highest area of the flash re
### **Known limitations**
-* All firmware projects can only build on Windows with the validated configuration below.
- * Cross-platform build support is work-in-progress.
-
**KabylakeOpenBoardPkg**
1. This firmware project has only been tested on the Intel KabylakeRvp3 board.
2. This firmware project has only been tested booting to Microsoft Windows 10 x64 with AHCI mode and Integrated Graphic
Device.
-3. This firmware project build has only been tested using the Microsoft Visual Studio 2015 compiler.
+3. The Windows build was tested on Windows 10 with Microsoft Visual Studio 2015.
+4. The Linux build was tested on Ubuntu 16.04.5 LTS with GCC version 5.4.0.
+5. The build was tested with NASM version 2.11.08.
**PurleyOpenBoardPkg**
1. This firmware project has only been tested on the Microsoft MtOlympus board.
@@ -228,9 +232,11 @@ Users can also flash the UEFI firmware image to the highest area of the flash re
**ClevoOpenBoardPkg**
1. Currently, support is only being added for the N1xxWU series of boards.
-2. The firmware project build has only been tested using the Microsoft Visual Studio 2015 compiler.
-3. The firmware project has not been tested on an actual board, it *should not* be expected to boot.
-4. The firmware project applies to all Clevo supported board configurations but is only being tested on System 76 Galago
+2. The Windows build was tested on Windows 10 with Microsoft Visual Studio 2015 compiler.
+3. The Linux build was tested on Ubuntu 16.04.5 LTS with GCC version 5.4.0.
+4. The build was tested with NASM version 2.11.08.
+5. The firmware project has not been tested on an actual board, it *should not* be expected to boot.
+6. The firmware project applies to all Clevo supported board configurations but is only being tested on System 76 Galago
Pro devices.
### **Planned Activities**
--
2.7.4
next prev parent reply other threads:[~2019-05-21 3:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 3:08 [edk2-platforms] [PATCH v2 0/5] Added GCC5 build support Agyeman, Prince
2019-05-21 3:08 ` [edk2-platforms] [PATCH v2 1/5] MinPlatformPkg: " Agyeman, Prince
2019-05-22 19:08 ` Kubacki, Michael A
2019-05-22 19:11 ` Nate DeSimone
2019-05-23 0:15 ` Chiu, Chasel
2019-05-21 3:08 ` [edk2-platforms] [PATCH v2 2/5] KabylakeSiliconPkg: Casting functions to EFIAPI Agyeman, Prince
2019-05-22 19:08 ` [edk2-devel] " Kubacki, Michael A
2019-05-22 19:11 ` Nate DeSimone
2019-05-23 0:18 ` Chiu, Chasel
2019-05-21 3:08 ` [edk2-platforms] [PATCH v2 3/5] KabylakeOpenBoardPkg: Added GCC5 build support Agyeman, Prince
2019-05-22 19:11 ` [edk2-devel] " Nate DeSimone
2019-05-23 0:19 ` Chiu, Chasel
2019-05-21 3:08 ` [edk2-platforms] [PATCH v2 4/5] ClevoOpenBoardPkg: " Agyeman, Prince
2019-05-22 19:11 ` [edk2-devel] " Nate DeSimone
2019-05-21 3:08 ` Agyeman, Prince [this message]
2019-05-21 3:20 ` [edk2-platforms] [PATCH v2 5/5] Intel/Readme.md: Updated readme with linux build instructions Chiu, Chasel
2019-05-22 19:06 ` [edk2-devel] " Kubacki, Michael A
2019-05-22 19:12 ` Nate DeSimone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3793b1cdad9c68d23ec1378f35f5fef9e4d42ced.1558406058.git.prince.agyeman@intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox