From: Supreeth Venkatesh <supreeth.venkatesh@arm.com>
To: edk2-devel@lists.01.org
Cc: eric.jin@intel.com, Supreeth Venkatesh <supreeth.venkatesh@arm.com>
Subject: [edk2-test] [PATCH 1/1] uefi-sct: Update "how to build" instructions.
Date: Thu, 11 Oct 2018 05:45:47 +0100 [thread overview]
Message-ID: <20181011044547.21300-1-supreeth.venkatesh@arm.com> (raw)
Update Build Instructions for UEFI SCTII AARCH64 (Linux) after
repository change.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Supreeth Venkatesh <supreeth.venkatesh@arm.com>
---
uefi-sct/HowToBuild/How to build SCT in UDK2017.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/uefi-sct/HowToBuild/How to build SCT in UDK2017.txt b/uefi-sct/HowToBuild/How to build SCT in UDK2017.txt
index 1a3bf1e8..146c9269 100644
--- a/uefi-sct/HowToBuild/How to build SCT in UDK2017.txt
+++ b/uefi-sct/HowToBuild/How to build SCT in UDK2017.txt
@@ -59,11 +59,11 @@ Linux Environment
Build Instructions for UEFI SCTII AARCH64 (Linux)
1) mkdir "sct_workspace"
2) cd sct_workspace
- 3) git clone https://github.com/UEFI/UEFI-SCT
+ 3) git clone https://github.com/tianocore/edk2-test.git
4) git clone https://github.com/tianocore/edk2
5) cd edk2
6) git checkout UDK2017
- 7) ln -s ../UEFI-SCT/SctPkg SctPkg
+ 7) ln -s ../edk2-test/uefi-sct/SctPkg SctPkg
8) cd ..
9) mkdir -p "tools/gcc"
10) cd "tools/gcc"
@@ -72,7 +72,7 @@ Build Instructions for UEFI SCTII AARCH64 (Linux)
13) cd ../..
14) export PATH=$PATH:"$PWD/tools/gcc/gcc-linaro-4.9-2016.02-x86_64_aarch64-linux-gnu/bin"
15) export CROSS_COMPILE="$PWD/tools/gcc/gcc-linaro-4.9-2016.02-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-"
- 16) ./SctPkg/build.sh AARCH64 GCC
+ 16) ../edk2-test/uefi-sct/SctPkg/build.sh AARCH64 GCC
Build EMS :
--
2.17.0
next reply other threads:[~2018-10-11 4:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 4:45 Supreeth Venkatesh [this message]
2018-10-11 5:43 ` [edk2-test] [PATCH 1/1] uefi-sct: Update "how to build" instructions Jin, Eric
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=20181011044547.21300-1-supreeth.venkatesh@arm.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