From: "Felix Polyudov" <felixp@ami.com>
To: "'Agyeman, Prince'" <prince.agyeman@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kubacki, Michael A" <michael.a.kubacki@intel.com>
Subject: Re: [edk2-devel] [edk2-platforms] Building a platform: which edk2 revision to choose?
Date: Tue, 18 Feb 2020 20:17:29 +0000 [thread overview]
Message-ID: <9333E191E0D52B4999CE63A99BA663A003FFBEBB18@atlms1.us.megatrends.com> (raw)
In-Reply-To: <MWHPR11MB14558B994F886E2E5425B85C9A150@MWHPR11MB1455.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 4613 bytes --]
Thank!
Builds fine with VS2015
From: Agyeman, Prince [mailto:prince.agyeman@intel.com]
Sent: Friday, February 14, 2020 12:09 PM
To: devel@edk2.groups.io; Felix Polyudov
Cc: Kubacki, Michael A; Gao, Liming
Subject: RE: [edk2-devel] [edk2-platforms] Building a platform: which edk2 revision to choose?
Hi Felix,
Try building with VS2015. There's a known issue with VS2017 builds as documented here https://bugzilla.tianocore.org/show_bug.cgi?id=2408
Thanks
Prince
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Felix Polyudov
Sent: Friday, February 14, 2020 8:01 AM
To: Agyeman, Prince <prince.agyeman@intel.com>; devel@edk2.groups.io
Cc: Kubacki, Michael A <michael.a.kubacki@intel.com>; Gao, Liming <liming.gao@intel.com>
Subject: Re: [edk2-devel] [edk2-platforms] Building a platform: which edk2 revision to choose?
I'm using the latest version for all the repositories:
ed2 : f1d78c489a399
edk2-platofrms: 41c1d9ba33046637e
edk2-non-osi : c10580aea501ee
FSP : e6177bb3bb57747d
I'm building the project using command "build_bios.py -p WhiskeylakeURvp -t VS2017 -r"
Here is the error I'm getting:
PeiPolicyUpdateLib.lib(PeiSaPolicyUpdatePreMem.obj) : error LNK2001: unresolved external symbol _gEfiMemoryTypeInformationGuid
From: Agyeman, Prince [mailto:prince.agyeman@intel.com]
Sent: Thursday, February 13, 2020 8:16 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Felix Polyudov
Cc: Kubacki, Michael A
Subject: RE: [edk2-platforms] Building a platform: which edk2 revision to choose?
Hi Felix,
Can you include a log or details of the build error you're seeing ?
Also what are the FSP , edk2-non-osi, edk2-platform and edk2 commit IDs you are using ?
Thanks
Prince
Prince
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> On Behalf Of Felix Polyudov
Sent: Thursday, February 13, 2020 3:11 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Cc: Kubacki, Michael A <michael.a.kubacki@intel.com<mailto:michael.a.kubacki@intel.com>>
Subject: [edk2-devel] [edk2-platforms] Building a platform: which edk2 revision to choose?
I'm trying to build one of the board packages from the edk2-platform repository.
(I'm building WhiskeylakeOpenBoardPkg, but I suspect the problem exists for most of the board packages).
The build process fails (I'm using build instructions from https://github.com/tianocore/edk2-platforms/tree/master/Platform/Intel).
I suspect this is happening because tip of the board package is not compatible with tip of the edk2 repo.
Is there a defined way for me to figure out the latest working revisions of the edk2 repo (or the other 2 repos that are part of the project) that I should use?
Thanks
Felix
P Please consider the environment before printing this email
The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.
P Please consider the environment before printing this email
The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.
Please consider the environment before printing this email.
The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.
[-- Attachment #2: Type: text/html, Size: 32106 bytes --]
next prev parent reply other threads:[~2020-02-18 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 23:10 [edk2-platforms] Building a platform: which edk2 revision to choose? Felix Polyudov
2020-02-14 1:16 ` Agyeman, Prince
2020-02-14 16:01 ` Felix Polyudov
2020-02-14 17:09 ` [edk2-devel] " Agyeman, Prince
2020-02-18 20:17 ` Felix Polyudov [this message]
2020-02-14 3:42 ` Liming Gao
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=9333E191E0D52B4999CE63A99BA663A003FFBEBB18@atlms1.us.megatrends.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