Apologies. I was out of the office yesterday. My guess is that you have multiple installs that may be confusing the “vswhere” utility. As such, you may have correctly configured your Buildtools

Can you provide your platform DSC file? What is your exact "build" command line? (I'm looking for the "-a", "-b", "-t" options.) Thanks Laszlo

Thanks, I must have messed up my testing then. ... Does it matter if we add "--zero" directly after "GenFw", as very first option? Probably not. I'll update the BZ (state that my testing was

Hi Bret & others, Do you have any comments on this?? pmdyounaskhan786@...> wrote:

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

Hi Caden, Great to meet you and welcome to the TianoCore project! Glad you hear you are interested! Sorry it has taken me a while to get back to you, researching the topics you are interested in

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,

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

If I manually call GenFw with -z then it does in fact work. Proof via diffoscope: https://try.diffoscope.org/takcczugyxzr.html I'm failing at making this actually stick in the makefiles

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

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

Hi Liming, I tried the "--zero" option myself (as seen in the BZ), but it didn't work. What I did was the following: in the original run of the "build" utility, I redirected the standard output and

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

Hi Everyone, I am pleased to announce that TianoCore has been accepted to participate in GSoC 2021! If you are a student and are interested in participating this year, feel free to introduce yourself

Hi, We’ve working with patch series on top of the QEMU CXL 2.0 Type 3 adding Data Object Exchange (DOE) for CDAT and Compliance Mode. This is required to support CXL 2.0 device enumeration and

adding Nate

Hi, We’ve released our patch series on top of the QEMU CXL 2.0 Type 3 adding Data Object Exchange (DOE) for CDAT and Compliance Mode. This is required to support CXL 2.0 device enumeration and

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

Hi Bret, I have installed using vs_buildtools.exe cmd in shared link ( https://microsoft.github.io/mu/CodeDevelopment/prerequisites/#visual-studio-2019-preferred ) Still I am facing the same build

Good afternoon. I'm trying to compile UEFI with UDK2018 for the ApolloLake E3900 platform, but it doesn't work. I made some changes to the source code, the compilation process has progressed further,