[Ace-users] [ace-users] Unresolved ACE_Time_Value symbols

[Stew Paddaso]

Thanks everyone for replying.

It turned out that our default VS property sheet was defining
_USE_32BIT_TIME_T, but ACE was built without this.

On 10/17/07, Johnny Willemsen <jwillemsen at remedy.nl> wrote:
> Hi,
>
> Maybe this is caused by some inconsistencies in the time_t definition. We
> had in the past long but switched to use time_t. Probably related to the
> change below.
>
> Regards,
>
> Johnny Willemsen
> Remedy IT
> Postbus 101
> 2650 AC  Berkel en Rodenrijs
> The Netherlands
> www.theaceorb.nl / www.remedy.nl
>
> *** Integrated compile and test statistics see
> http://scoreboard.theaceorb.nl ***
> *** Commercial service and support for ACE/TAO/CIAO             ***
> *** See http://www.theaceorb.nl/en/support.html                 ***
>
>
> Wed Mar 22 18:42:36 UTC 2006  Ossama Othman  <ossama_othman at symantec dot
> com>
>
>         From Russell Mora <russell_mora at symantec dot com>
>         * ace/Time_Value.inl:
>
>           With MSVC8 the type of time_t is by default 64-bit unless
>           _USE_32BIT_TIME_T is defined - changed #ifdef to recognise this
>           and also changed other set() methods to use the version that
>           knows how to handle the 64-bit type.
>
> "Stew Paddaso" <stew.paddaso at gmail.com> wrote in message
> news:<mailman.2558.1192579261.5286.ace-users at mail.cse.wustl.edu>...
> > Abdullah,
> >
> > Thank you for the reply.
> >
> > However, I am linking against the ACE library that was built using the
> > provided VC8 solution file.  The ACE library I am using has been used
> > several other times by other developers in our group. I'm happen to be
> > the first to use the ACE_Time_Value class.
> >
> > I use many other ACE classes in my code, but these are the only
> > reported linker errors.
> >
> > -Stew
> >
> > On 10/16/07, Abdullah Sowayan <abdullah.sowayan at lmco.com> wrote:
> >
> > > Hi,
> > >
> > > Thanks for using the PRF form. Are you using VS2005 express,
> > > professional, or enterprise edition?
> > >
> > > At first glance, it seems to me that you're not linking in the ACE
> > > library. Are you using MPC to generate your solution or are you manually
> > > doing it? If you're manually do it, I highly suggest that you use MPC to
> > > avoid such problems in the future.
> > >
> > > Thanks,
> > > Abdul
> >
> > On 10/16/07, Stew Paddaso <stew.paddaso at gmail.com> wrote:
> > > ACE VERSION : 5.5.1
> > >
> > > HOST MACHINE and OPERATING SYSTEM:
> > >        Intel Pentium4 - WinXP
> > >
> > > COMPILER NAME AND VERSION (AND PATCHLEVEL):
> > >        VisualStudio 2005 (VC8)
> > >
> > > THE $ACE_ROOT/ace/config.h FILE:
> > >        #include "ace/config-win32.h"
> > >
> > > DESCRIPTION:
> > >
> > > I get the following link errors when I build my project:
> > >
> > > SystemClock.obj : error LNK2019: unresolved external symbol
> > > "__declspec(dllimport) public: long __thiscall
> > > ACE_Time_Value::sec(void)const " (__imp_?sec at ACE_Time_Value@@QBEJXZ)
> > > referenced in function "public: virtual unsigned __int64 const
> > > __thiscall MPF::SystemClockAbs::GetTime(void)"
> > > (?GetTime at SystemClockAbs@MPF@@UAE?B_KXZ)
> > >
> > > SystemClock.obj : error LNK2019: unresolved external symbol
> > > "__declspec(dllimport) public: __thiscall
> > > ACE_Time_Value::ACE_Time_Value(long,long)"
> > > (__imp_??0ACE_Time_Value@@QAE at JJ@Z) referenced in function "public:
> > > virtual unsigned __int64 const __thiscall
> > > MPF::SystemClockAbs::GetTime(void)"
> > > (?GetTime at SystemClockAbs@MPF@@UAE?B_KXZ)
> > >
> > >
> > > What is strange to me is that I'm using other ACE_Time_Value methods,
> such as:
> > > msec
> > > usec
> > > operator=
> > > operator+
> > >
> > > but the linker is finding those symbols. Any ideas?
> > >
> >
>
>