Re: [Boost-users] date_time clocks, microsec_clock, etc

From: Aaron W. LaFramboise (aaronrabiddog51_at_[hidden])
Date: 2004-05-06 23:50:17

Victor A. Wagner Jr. wrote:

> PossibleClockEnhancements.obj : error LNK2019: unresolved external 
> symbol __imp__timeGetTime_at_0 referenced in function "public: static 
> void __cdecl gettickcount_timer::warm(void)" 
> (?warm_at_gettickcount_timer@@SAXXZ)
> PossibleClockEnhancements.obj : error LNK2019: unresolved external 
> symbol __imp__timeBeginPeriod_at_4 referenced in function "public: static 
> void __cdecl timegettime_timer::warm(void)" 
> (?warm_at_timegettime_timer@@SAXXZ)
> Release/PossibleClockEnhancements.exe : fatal error LNK1120: 2 
> unresolved externals

Its traditional on Windows to not link against the 'winmm' library by 
default.  You need to add winmm.lib or whatever to the link line.  That 
is one unfortunate downside to using this timer that is otherwise 
traditionally very well-supported and stable and precise in comparison 
to the alternatives.

Aaron