Wenyi, As the description in Commit 01b6090b, the change was to fix the incremental build issue in the MSVC toolchain. But now it‘s found that impacts the usage of the GCC toolchain. Please file a BZ

Hi, liming, Yes, my command using 2>&1 to redirect strerr to stdout, and after updating to version 202011 the stderr are not shown in the screen but only written in xxx.log. According to Laszlo's help

Hi, Laszlo, Thank you very much for such detailed explanation. I know the root cause of the problem now. -----邮件原件----- 发件人: Laszlo Ersek [mailto:lersek@...] 发送时间: 2021年3月18日 4:31 收件人: discuss@edk2.gr

Wenyi: Do you use build command to build your platform and find the message from stderr are not shown in the screen? Thanks Liming > -----邮件原件----- > 发件人: discuss@edk2.groups.io <discuss@edk2.groups.i

Hello, I ran into a windows booting failure issue(a page fault exception), and narrow down it to the following patch, MdeModulePkg/DxeIpl: support more NX related PCDs https://github.com/tianocore/edk

Hi, I have just completed a fork of the GPLv2 ntfs-3g project [1], that enables compiling it as a UEFI driver. The project, as well as binary releases (for X64, IA32, AARCH64 and ARM), can be found at

Hi，everyone， I used to set makeflags like below,so that only message from stderr will be shown in console while compiling, and at the same time message from stderr and stdout will all be saved in xxx.

Hello, My name is Caden Kline. I am a freshmen Computer Science major in the US. I intend to specialize in Systems or Security or both. The main two tasks I am hoping to apply for are "Terminal driver

Yes. Just RELEASE_*_*_GENFW_FLAGS = --zero The format is defined in DSC spec. = means append, == means replacement. Thanks Liming > -----邮件原件----- > 发件人: Ross Burton <ross@...> > 发送时间: 2021年3月17日 0:27

Hi everyone, I am Vikas Kundu, a post-grad student of Computer Science in India. I can code in Python, node.js, C and C++ and is aware of networking concepts especially DNS. I wish to work on the UEFI

Ross: I verify -z option. It can remove DEBUG entry and make sure the generated image be reproduced. PlatformPkg.dsc: [BuildOptions] RELEASE_*_*_GENFW_FLAGS = -z Thanks Liming > -----邮件原件----- > 发件人:

Hello, I am interested in a UEFI Redfish Host Interface that does not require an OS. That is, the Redfish service would be provided by UEFI itself (via an IP interface)... or perhaps an EFI applicatio

Andrew: > -----邮件原件----- > 发件人: discuss@edk2.groups.io <discuss@edk2.groups.io> 代表 Andrew > Fish via groups.io > 发送时间: 2021年3月16日 2:56 > 收件人: discuss <discuss@edk2.groups.io>; ross@... > 抄送: Feng, Bob

Ross: This solution is for the reproduced binary images. If your platform has this request, you can update the platform DSC [BuildOptions] to include the option RELEASE_*_*_GENFW_FLAGS=-z. Thanks Limi

Hi, As per https://bugzilla.tianocore.org/show_bug.cgi?id=3256, GenFw writes non-reproducible binaries by embedding a build path. In fact in a build of ovmf with embedded shell, this one path is the s

Updated (below)… - Bret Sent: Monday, March 8, 2021 8:09 AM To: Mohammad Younas Khan Pathan<mailto:pmdyounaskhan786@...> Cc: discuss@edk2.groups.io<mailto:discuss@edk2.groups.io>; Sean Brogan<mailto:s

Laszlo: I verify the below three commands. The first generated EFI image includes DEBUG entry. Other EFI images have no DEBUG entry. Yes, DEBUG entry is added by GenFw tool. -z option can be used to r

So where would I put that statement? I tried dropping it into ShellPkg.dsc but it wasn't respected. Ross

RELEASE_*_*_GENFW_FLAGS = -z means this option is applied on RELEASE build. *_*_*_GANFW_FLAGS = -z can apply this option to all target builds. When you build, you can build -j build.log. Then, build l

I tried adding that to ShellPkg.dsc but I can't seem to make the value actually get into the build. Is there anything else I need to do apart from: +++ b/ShellPkg/ShellPkg.dsc @@ -154,3 +154,4 @@ [Bui