From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: devel@edk2.groups.io
Cc: Bob Feng <bob.c.feng@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Yuwei Chen <yuwei.chen@intel.com>,
Sean Brogan <sean.brogan@microsoft.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: [PATCH v1 3/5] BaseTools: Add reference to new build instructions
Date: Mon, 5 Dec 2022 12:28:37 -0500 [thread overview]
Message-ID: <20221205172839.2859-4-mikuback@linux.microsoft.com> (raw)
In-Reply-To: <20221205172839.2859-1-mikuback@linux.microsoft.com>
From: Michael Kubacki <michael.kubacki@microsoft.com>
Adds a reference to the new build instructions on the TianoCore wiki
that currently describe building with containers and Stuart.
Cc: Bob Feng <bob.c.feng@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Cc: Yuwei Chen <yuwei.chen@intel.com>
Cc: Sean Brogan <sean.brogan@microsoft.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
---
BaseTools/ReadMe.rst | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/BaseTools/ReadMe.rst b/BaseTools/ReadMe.rst
index de85ca4be65e..592be51b1fcd 100644
--- a/BaseTools/ReadMe.rst
+++ b/BaseTools/ReadMe.rst
@@ -1,3 +1,13 @@
+::
+
+ Note: New build instructions are available. It is recommended to start with
+ the new instructions if learning how to build edk2 and/or BaseTools for the
+ first time. This page is retained for reference.
+
+New instructions: `Build Instructions`_
+
+.. _`Build Instructions`: https://github.com/tianocore/tianocore.github.io/wiki/Build-Instructions
+
This directory contains the EDK II build tools and template files.
Templates are located in the Conf directory, while the tools executables for
Microsoft Windows Operating Systems are located in the Bin\\Win32 directory, other
@@ -23,9 +33,6 @@ After this, you can run the toolsetup.bat file, which is in the same
directory as this file. It should setup the remainder of the environment,
and build the tools if necessary.
-Please also refer to the ``BuildNotes.txt`` file for more information on
-building under Windows.
-
Unix-like operating systems
===========================
--
2.28.0.windows.1
next prev parent reply other threads:[~2022-12-05 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 17:28 [PATCH v1 0/5] Update references to new edk2 build instructions Michael Kubacki
2022-12-05 17:28 ` [PATCH v1 1/5] .pytool/Readme.md: Add reference to new " Michael Kubacki
2022-12-05 17:28 ` [PATCH v1 2/5] ArmVirtPkg: " Michael Kubacki
2022-12-05 17:28 ` Michael Kubacki [this message]
2022-12-05 17:28 ` [PATCH v1 4/5] EmulatorPkg: " Michael Kubacki
2022-12-05 17:28 ` [PATCH v1 5/5] OvmfPkg: " Michael Kubacki
2022-12-09 7:00 ` Yao, Jiewen
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=20221205172839.2859-4-mikuback@linux.microsoft.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