MdeModulePkg.dsc is for package build test, no functionality verification.
If you want to verify some module in this Package, you can add it into the platform, such as Nt32 or Ovmf, then see its functionality. >-----Original Message----- >From: edk2-devel [mailto:[email protected]] On Behalf Of >david moheban >Sent: Saturday, September 09, 2017 1:33 AM >To: [email protected] >Subject: Re: [edk2] WARNING: No source level debug > >I checked all of the DebugLib instances and I believe they are all there >though in different locations in Mdemodulepkg.dsc vs nt32pkg.dsc. I have >tried every suggestion and made every configuration change possible. Spent >hours google searching the issue. Getting rid of the Null debuglib >reference, using the intel package vs mdepkg and so on. Sorting it out >further unfortunately is beyond my abilities at the moment. I think the >issue is that the debug calls get ignored because a driver based on >Mdemodulepkg is running off of the NT32pkg firmware volume image I copied >from the NT32 build X64 folder into the Mdemodulepkg build x64 folder along >with SecMain so that the VM can run when I type 'Build run -p >mdemodulepkg'. If there is another way to rebuild that firmware volume >someone please clue me in because i think that would fix it. I only know >how to build it from Nt32pkg. In anycase Ill just start over and use the >NT32pkg platform instead. > >Thank you > >Sent from my iPad >_______________________________________________ >edk2-devel mailing list >[email protected] >https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
