public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sean" <sean.brogan@microsoft.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Navdeeppal.Singh@dell.com" <Navdeeppal.Singh@dell.com>,
	Bret Barkelew <Bret.Barkelew@microsoft.com>,
	"jim.slaughter@sage-micro.com" <jim.slaughter@sage-micro.com>
Subject: Re: [EXTERNAL] [edk2-devel] EDK2 environment setup
Date: Thu, 23 Apr 2020 19:03:20 +0000	[thread overview]
Message-ID: <MW2PR2101MB0924FF848C48AFCA513D5B52E1D30@MW2PR2101MB0924.namprd21.prod.outlook.com> (raw)
In-Reply-To: <54a4f7933a1c4c0ea0eb34b43b837fb2@BLRX13MDC402.AMER.DELL.COM>

[-- Attachment #1: Type: text/plain, Size: 3335 bytes --]

Navdeep,

Yes since the 202002 stable tag there have been submodules introduced to the basetools.  If you look closely you will see in the CI process this required a change where stuart_setup is run before calling edk2toolsbuild.py.

https://github.com/tianocore/edk2/commit/e1fbff3ded87704fb0086f9b5fb368080eb4db51#diff-6973939bf9ad6f6a3082d99ce3b32ff1


If you are using "stuart" to build then that is the suggested path as stuar_setup will init your submodules listed in the RequiredSubmodules (https://github.com/tianocore/edk2/blob/master/.pytool/CISettings.py#L136).  Given that the edk2 project and ecosystem has numerous ways to setup your environment and build, you can also just make sure your workspace is complete prior to running Edk2ToolsBuild.py.  In this case you only need to run "git submodule update --init"

I just did this and it works fine with VS2019.

Jim,

Just as fyi as I know there are lots of reasons for toolchain selection.
I believe the Visual studio build tools are available free of charge (not the IDE but the compilers).   Directions here. https://microsoft.github.io/mu/CodeDevelopment/prerequisites/#visual-studio-2019-preferred

Thanks
Sean



From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Navdeeppal.Singh via groups.io
Sent: Thursday, April 23, 2020 9:14 AM
To: Bret Barkelew <Bret.Barkelew@microsoft.com>; devel@edk2.groups.io
Subject: Re: [EXTERNAL] [edk2-devel] EDK2 environment setup

Hi Bret,
Yes PIP requirements are up to date.
On further digging through the logging file BASETOOLS_BUILD.txt.
INFO - subprocess not exit successfully
INFO - Error while execute command 'nmake all' in direcotry C:\edk2\BaseTools\Source\C\BrotliCompress

Regards,
Navdeep

From: Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Sent: Thursday, April 23, 2020 9:37 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Singh, Navdeeppal
Subject: RE: [EXTERNAL] [edk2-devel] EDK2 environment setup


[EXTERNAL EMAIL]
Have you installed the up-to-date Python requirements? "pip install -upgrade -r pip-requirements.txt"?

That's the first thing I would check. Otherwise, happy to look at the problem with you.

- Bret

From: NAVDEEPPAL_SINGH via groups.io<mailto:NAVDEEPPAL_SINGH=DELL.COM@groups.io>
Sent: Thursday, April 23, 2020 6:05 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: [EXTERNAL] [edk2-devel] EDK2 environment setup

I am trying to setup EDK2 environment setup from Tianocore/EDK2.
While doing the Base Tool setup. After running BaseTool/EDK2ToolsBuild.py -t VS2019
Getting following error :-
c:\edk2\BaseTools>python Edk2ToolsBuild.py  -t VS2019
SECTION - Init SDE
SECTION - Loading Plugins
SECTION - Start Invocable Tool
Traceback (most recent call last):
  File "Edk2ToolsBuild.py", line 177, in <module>
    main()
  File "Edk2ToolsBuild.py", line 173, in main
    Edk2ToolsBuild().Invoke()
  File "C:\Program Files\Python38\lib\site-packages\edk2toolext\base_abstract_invocable.py", line 141, in Invoke
    retcode = self.Go()
  File "Edk2ToolsBuild.py", line 139, in Go
    raise Exception("Failed to build.")
Exception: Failed to build.

set EDK_TOOLS_PATH=C:\edk2\BaseTools
set EDK_TOOLS_BIN=C:\edk2\BaseTools\Bin\Win32
Can some one help



[-- Attachment #2: Type: text/html, Size: 8063 bytes --]

  parent reply	other threads:[~2020-04-23 19:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 12:38 EDK2 environment setup NAVDEEPPAL_SINGH
2020-04-23 16:07 ` [EXTERNAL] [edk2-devel] " Bret Barkelew
2020-04-23 16:14   ` Navdeeppal.Singh
2020-04-23 16:17     ` Bret Barkelew
2020-04-23 16:21       ` Navdeeppal.Singh
2020-04-23 16:34         ` Bret Barkelew
2020-04-23 17:26           ` Michael D Kinney
2020-04-23 18:23             ` Bret Barkelew
2020-04-23 19:03     ` Sean [this message]
2020-04-27  8:26       ` Navdeeppal.Singh
2020-04-27 20:57         ` Sean
2020-04-28  9:15           ` Navdeeppal.Singh
2020-04-28  9:35             ` Guomin Jiang
2020-04-28  9:47               ` Leif Lindholm
2020-04-28  9:52                 ` Navdeeppal.Singh
2020-04-30  5:09                   ` Navdeeppal.Singh
2020-05-04  5:17                     ` Navdeeppal.Singh
2020-05-04 17:40                       ` Sean
2020-05-04 18:47                       ` Andrew Fish
2020-04-28  9:38             ` [edk2-devel] EmulatorPkg WinHost build failure with VS2019 Was: " Leif Lindholm
2020-04-23 16:23   ` [EXTERNAL] [edk2-devel] " jim slaughter
2020-04-23 16:27     ` Bret Barkelew

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=MW2PR2101MB0924FF848C48AFCA513D5B52E1D30@MW2PR2101MB0924.namprd21.prod.outlook.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