On Thu, Aug 15, 2013 at 11:57 PM, Laszlo Ersek <[email protected]> wrote:
> On 08/16/13 06:41, Hamel, Lee M wrote:
>> I have a DEBUG macro call DEBUG((DEBUG_INFO, ........
>>
>> In a DEBUG build, the string appears in the serial console, while in
>> RELEASE build it does not.
>>
>> Does anyone know why this is the case?
>
> Well at least in case of OVMF, the OvmfPkg/OvmfPkgX64.dsc file says:
>
> [BuildOptions]
> ...
> GCC:RELEASE_*_*_CC_FLAGS = -DMDEPKG_NDEBUG
> INTEL:RELEASE_*_*_CC_FLAGS = /D MDEPKG_NDEBUG
> MSFT:RELEASE_*_*_CC_FLAGS = /D MDEPKG_NDEBUG
>
Yep. But, this can be undone for a single driver with an override like:
Path/To/Driver.inf {
<BuildOptions>
MSFT:*_*_*_CC_FLAGS = /UMDEPKG_NDEBUG
GCC:*_*_*_CC_FLAGS = -UMDEPKG_NDEBUG
}
But, note that this will not undefine MDEPKG_NDEBUG for libraries used
by the driver. So, you might need to specify a similar override for a
library's .inf.
-Jordan
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel