From: Michael D Kinney <michael.d.kinney@intel.com>
To: edk2-devel@lists.01.org
Cc: Leif Lindholm <leif.lindholm@linaro.org>,
Kelly Steele <kelly.steele@intel.com>
Subject: [Patch 2/2] QuarkPlatformPkg/Readme.md: edk2-non-osi directory layout
Date: Wed, 9 Aug 2017 12:39:57 -0700 [thread overview]
Message-ID: <20170809193957.10644-3-michael.d.kinney@intel.com> (raw)
In-Reply-To: <20170809193957.10644-1-michael.d.kinney@intel.com>
The following commit moved the QuarkSocBinPkg from the root
directory to the the Silicon/Intel directory.
https://github.com/tianocore/edk2-non-osi/commit/182e85d04566800fe188de4b1c30a50533dd74b7
The following updates are made to Readme.md:
* PACKAGES_PATH setting for edk2-non-osi directory changes
* Remove use of edk2-FatPkg repository
* Remove use of edk2-BaseTools-win32 repository
* Run python build tools from sources
Cc: Leif Lindholm <leif.lindholm@linaro.org>
Cc: Kelly Steele <kelly.steele@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
---
QuarkPlatformPkg/Readme.md | 34 ++++++++++++++++++----------------
1 file changed, 18 insertions(+), 16 deletions(-)
diff --git a/QuarkPlatformPkg/Readme.md b/QuarkPlatformPkg/Readme.md
index f925f9ef27..aa9d9856bd 100644
--- a/QuarkPlatformPkg/Readme.md
+++ b/QuarkPlatformPkg/Readme.md
@@ -46,12 +46,12 @@
- Install
* ASL compiler: Available from http://www.acpica.org
- Install into ```C:\ASL``` to match default tools_def.txt configuration.
+* Python 2.7: Available from http://www.python.org
Create a new directory for an EDK II WORKSPACE.
The code block below shows the GIT clone operations required to pull the EDK II
-source tree, the FatPkg sources, the pre-built versions of BaseTools as WIN32
-binaries, and the edk2-non-osi repository that provides a binary file for the
+source tree and the edk2-non-osi repository that provides a binary file for the
Quark Remote Management Unit (RMU).
Next it sets environment variables that must be set before running
@@ -60,6 +60,8 @@ the EDK II [Multiple Workspace](
https://github.com/tianocore/tianocore.github.io/wiki/Multiple_Workspace)
feature is used.
+Next, the EDK II BaseTools required to build firmware images are built.
+
Next, the ```edksetup.bat``` file is run to complete the initialization of an
EDK II build environment. Two example build commands are shown. The first one
in ```QuarkPlatformPlg/Quark.dsc``` builds a full UEFI firmware image that is
@@ -69,16 +71,17 @@ image that is useful for initial power-on and debug of new features.
```cmd
git clone https://github.com/tianocore/edk2.git
-git clone https://github.com/tianocore/edk2-FatPkg.git FatPkg
-git clone https://github.com/tianocore/edk2-BaseTools-win32.git
git clone https://github.com/tianocore/edk2-non-osi.git
+set PYTHON_HOME=c:\Python27
set WORKSPACE=%CD%
-set PACKAGES_PATH=%WORKSPACE%\edk2;%WORKSPACE%\edk2-non-osi
-set EDK_TOOLS_BIN=%WORKSPACE%\edk2-BaseTools-win32
+set PACKAGES_PATH=%WORKSPACE%\edk2;%WORKSPACE%\edk2-non-osi\Silicon\Intel
+set EDK_TOOLS_PATH=%WORKSPACE%\edk2\BaseTools
+cd %WORKSPACE%\edk2
-cd edk2
-edksetup.bat
+BaseTools\toolsetup.bat Rebuild
+
+edksetup.bat Rebuild
build -a IA32 -t VS2015x86 -p QuarkPlatformPkg/Quark.dsc
build -a IA32 -t VS2015x86 -p QuarkPlatformPkg/QuarkMin.dsc
@@ -91,12 +94,13 @@ build -a IA32 -t VS2015x86 -p QuarkPlatformPkg/QuarkMin.dsc
* GIT client
* GCC 4.9 compiler
* ASL compiler: Available from http://www.acpica.org.
+* Python 2.7
Create a new directory for an EDK II WORKSPACE.
The code block below shows the GIT clone operations required to pull the EDK II
-source tree, the FatPkg sources, and the edk2-non-osi repository that provides a
-binary file for the Quark Remote Management Unit (RMU).
+source tree and the edk2-non-osi repository that provides a binary file for the
+Quark Remote Management Unit (RMU).
Next it sets environment variables that must be set before running
```edksetup.bat```. Since content is being pulled from multiple repositories,
@@ -106,7 +110,7 @@ feature is used.
Next, the EDK II BaseTools required to build firmware images are built.
-Next, the ```edksetup.bat``` file is run to complete the initialization of an
+Next, the ```edksetup.sh``` file is run to complete the initialization of an
EDK II build environment. Two example build commands are shown. The first one
in ```QuarkPlatformPlg/Quark.dsc``` builds a full UEFI firmware image that is
able to boot the built-in UEFI Shell and Linux from a micro SD FLASH card. The
@@ -115,17 +119,15 @@ image that is useful for initial power-on and debug of new features.
```sh
git clone https://github.com/tianocore/edk2.git
-git clone https://github.com/tianocore/edk2-FatPkg.git FatPkg
git clone https://github.com/tianocore/edk2-non-osi.git
export WORKSPACE=$PWD
-export PACKAGES_PATH=$WORKSPACE/edk2:$WORKSPACE/edk2-non-osi
+export PACKAGES_PATH=$WORKSPACE/edk2:$WORKSPACE/edk2-non-osi/Silicon/Intel
export EDK_TOOLS_PATH=$WORKSPACE/edk2/BaseTools
-
-make -C edk2/BaseTools
-
cd $WORKSPACE/edk2
+make -C BaseTools
+
. edksetup.sh BaseTools
build -a IA32 -t GCC49 -p QuarkPlatformPkg/Quark.dsc
--
2.13.1.windows.2
next prev parent reply other threads:[~2017-08-09 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 19:39 [Patch 0/2] Update Quark for edk2-non-osi changes Michael D Kinney
2017-08-09 19:39 ` [Patch 1/2] QuarkSocPkg/MemoryInit: Remove use of memset()/memcpy() Michael D Kinney
2017-08-10 16:37 ` Steele, Kelly
2017-08-09 19:39 ` Michael D Kinney [this message]
2017-08-10 8:40 ` [Patch 2/2] QuarkPlatformPkg/Readme.md: edk2-non-osi directory layout Leif Lindholm
2017-08-10 16:37 ` Steele, Kelly
2017-08-10 16:38 ` [Patch 0/2] Update Quark for edk2-non-osi changes Steele, Kelly
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=20170809193957.10644-3-michael.d.kinney@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