[omniORB] Compile omniOBR-4.0.1 using .NET 2005(VC 8.0) compiler

[S. Sahayaraj]

Tried to compile the omniORB-4.0.7 on VC8 along with STLPort. I'm
getting the following linking errors. Would it be a known issue OR any
workaround is available. Kindly let me know that.

Thanks
Sahay.

Namingdynstub.o : error LNK2001: unresolved external symbol "public:
virtual voi

d __thiscall CosNaming::NamingContext::CannotProceed::_raise(void)const
" (?_rai

se at CannotProceed@NamingContext at CosNaming@@UBEXXZ)

Namingdynstub.o : error LNK2001: unresolved external symbol "private:
virtual ch

ar const * __thiscall
CosNaming::NamingContext::CannotProceed::_NP_repoId(int *)

const " (?_NP_repoId at CannotProceed@NamingContext at CosNaming@@EBEPBDPAH at Z)

Namingdynstub.o : error LNK2001: unresolved external symbol "private:
virtual vo

id __thiscall CosNaming::NamingContext::CannotProceed::_NP_marshal(class
cdrStre

am &)const "
(?_NP_marshal at CannotProceed@NamingContext at CosNaming@@EBEXAAVcdrStre

am@@@Z)

Namingdynstub.o : error LNK2001: unresolved external symbol "public:
virtual cla

ss CORBA::Exception * __thiscall
CosNaming::NamingContext::CannotProceed::_NP_du

plicate(void)const "
(?_NP_duplicate at CannotProceed@NamingContext at CosNaming@@UBEP

AVException at CORBA@@XZ)

Namingdynstub.o : error LNK2001: unresolved external symbol "private:
virtual ch

ar const * __thiscall
CosNaming::NamingContext::CannotProceed::_NP_typeId(void)c

onst " (?_NP_typeId at CannotProceed@NamingContext at CosNaming@@EBEPBDXZ)

Namingdynstub.o : error LNK2019: unresolved external symbol "public:
virtual __t

hiscall CosNaming::NamingContext::CannotProceed::~CannotProceed(void)"
(??1Canno

tProceed at NamingContext@CosNaming@@UAE at XZ) referenced in function
"public: virtua

l void * __thiscall CosNaming::NamingContext::CannotProceed::`scalar
deleting de

structor'(unsigned int)"
(??_GCannotProceed at NamingContext@CosNaming@@UAEPAXI at Z)

shared\omniDynamic401_rt.dll : fatal error LNK1120: 632 unresolved
externals
 

-----Original Message-----
From: Duncan Grisby [mailto:duncan at grisby.org] 
Sent: Wednesday, June 21, 2006 9:34 PM
To: S. Sahayaraj
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] Compile omniOBR-4.0.1 using .NET 2005(VC 8.0)
compiler 

On Monday 12 June, "S. Sahayaraj" wrote:

> We just want to use omniORB-4.0.1 only and  don't want to change the
> omniORB-4.0.1 to 4.0.7. 
> 
> Can we compile the 4.0.1 code base with required changes done in .mk 
> files?. OR is it compulsory to change it 4.0.7 for VC8 support?.

It is much better if you use 4.0.7. I think there were several minor
changes to support VC8, in addition to the new platform file, so you
will have to do some modifications if you're determined to stick with
4.0.1.

Why do you want to stick with 4.0.1?  I can understand that you would
want to avoid possible regressions, but if you're using a totally new
compiler, I'm sure you're going to have to do a full regression test
anyway.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --