mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH] Documentation: efi: update SnpDxe build instructions
Date: Wed,  7 Oct 2020 11:51:09 +0200	[thread overview]
Message-ID: <20201007095109.23370-1-p.zabel@pengutronix.de> (raw)

Some sources have been moved into git submodules and SnpDxe was
moved from MdeModulePkg to NetworkPkg.

Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
---
 Documentation/boards/efi.rst | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/boards/efi.rst b/Documentation/boards/efi.rst
index f04b1d32378b..b12433014ef1 100644
--- a/Documentation/boards/efi.rst
+++ b/Documentation/boards/efi.rst
@@ -294,18 +294,19 @@ HOWTOs in the net, for example on http://tianocore.sourceforge.net/wiki/Using_ED
 
   git clone git://github.com/tianocore/edk2.git
   cd edk2
+  git submodule update --init
   make -C BaseTools
   . edksetup.sh
 
 At least the following lines in ``Conf/target.txt`` should be edited::
 
-  ACTIVE_PLATFORM = MdeModulePkg/MdeModulePkg.dsc
+  ACTIVE_PLATFORM = NetworkPkg/NetworkPkg.dsc
   TARGET_ARCH = X64
   TOOL_CHAIN_TAG = GCC48
   MAX_CONCURRENT_THREAD_NUMBER = 4
 
 The actual build is started with invoking ``build``. After building
-``Build/MdeModule/DEBUG_GCC48/X64/SnpDxe.efi`` should exist.
+``Build/NetworkPkg/DEBUG_GCC48/X64/SnpDxe.efi`` should exist.
 
 **NOTE** As of this writing (July 2014) the following patch was needed to
 compile EDK2.
-- 
2.20.1


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2020-10-07  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07  9:51 Philipp Zabel [this message]
2020-10-09  6:49 ` Sascha Hauer

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-all 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=20201007095109.23370-1-p.zabel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --subject='Re: [PATCH] Documentation: efi: update SnpDxe build instructions' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox