Re: WinHost.exe from EmulatorPkg and StdLib applications
Mike --toggle quoted messageShow quoted text
I moved my !include StdLib.inc to the very end of EmulatorPkg.dsc and I
found that the build issues went away. But if I included it before the
[BuildOptions] line, it would have trouble with the header files. My guess
is there is an order dependency about the way that the CC_FLAGS items are
MSFT:DEBUG_*_*_CC_FLAGS = /Od /Oy-
MSFT:NOOPT_*_*_CC_FLAGS = /Od /Oy-
MSFT:*_*_*_DLINK_FLAGS = /ALIGN:4096 /FILEALIGN:4096
MSFT:DEBUG_*_*_DLINK_FLAGS = /EXPORT:InitializeDriver=$(IMAGE_ENTRY_POINT)
MSFT:NOOPT_*_*_DLINK_FLAGS = /EXPORT:InitializeDriver=$(IMAGE_ENTRY_POINT)
I did try your changes with VS2017 and VS2015 and ran WinHost with both with
no trouble. And now I have my StdLib apps working too!
From: Kinney, Michael D <michael.d.kinney@...>
Sent: Thursday, July 25, 2019 9:13 AM
To: firstname.lastname@example.org; tim.lewis@...; Kinney, Michael D
Subject: RE: [edk2-discuss] WinHost.exe from EmulatorPkg and StdLib
I happened to be looking at this over the weekend.
I was able to resolve the build issues for XCODE5 for the IA32 version of
EmulatorPkg, but not X64.
I did not verify if it boots yet, so maybe you can help verify that.
A WIP branch with what I got working is here:
It also fixes some VS2017/VS2015 issues with EmulatorPkg.