Re: [edk2] TimerLib in StdLib

Subject: Re: [edk2] TimerLib in StdLib

From: Andrew Fish <>


Date: 2011-07-08 16:20:06


This issue came up last week. The TimerLib also breaks the OS Hosted emulators. For NT32 you need to point it to the NULL TimerLib, for EmulatorPkg (Unix, OS X) you need to point it to the emulator version of the Timerlib. So the short term solution is to use a NULL Timerlib, while this issue is being worked by the developer.  

Andrew Fish

On Jul 8, 2011, at 6:54 AM, Cohen, Eugene wrote:

I think that I may once again be on an out of date snapshot of edk2... apologies in advance if this is the case.

If you look in the latest .DSC file you will see the comments about needing to point to a NULL version of the TimerLib. 

From: Cohen, Eugene 
Sent: Friday, July 08, 2011 7:45 AM
Subject: [edk2] TimerLib in StdLib
I tried building StdLib and found a dependency in a couple infs on the TimerLib:
Find all "timerlib", Subfolders, Keep modified files open, Find Results 1, "d:\edk2\StdLib", "*.inf"
  D:\edk2\StdLib\LibC\LibC.inf(103):  TimerLib
  D:\edk2\StdLib\LibC\Time\Time.inf(44):  TimerLib
Since time is architectural to UEFI accessible through Runtime Services, I dont think StdLib should depend on TimerLib which is platform or processor-specific.
Can this dependency be removed?
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
edk2-devel mailing list