[omniORB] compiling omniORB3 on NT

[Lutz Bichler]

----- Original Message -----
From: Ji-Yong D. Chung <virtualcyber@erols.com>
To: <omniorb-list@uk.research.att.com>
Sent: Wednesday, October 13, 1999 6:43 PM
Subject: [omniORB] compiling omniORB3 on NT


>     This time, I compiled up to, but not including:
>
>     <top>/src/lib/omniORB2/dynamic/sharedlib
>
>
>     The compiler says:
>
>
>
../../../../../bin/x86_win32/clwrapper -gnuwin32 -c -O2 -MD -GX -DNTArchi=
tec
>
ture   -I./.. -I./../.. -I./../../.. -DUSE_omniORB_logStream -D_OMNIORB_D=
YNA
>
MIC_LIBRARY -I.  -I../../../../../include -D__WIN32__ -D__x86__ -D__NT__ =
-D_
> _OSVERSION__=3D4 -Foany.o ../any.cc
> any.cc
> ..\..\..\..\..\include\omniORB3/CORBA.h(796) : error C2201: 'OMGVMCID' =
:
> must have external linkage in order to be exported/imported
> ..\..\..\..\..\include\omniORB3/poa.h(265) : error C2201:
'THREAD_POLICY_ID'
> : must have external linkage in order to be exported/imported
>
> and more error messages.
>
>
>     Strangely, I did not get these errors when I compiled orbcore, even
> though files in orbcore still refers to OMGVMCID, THREAD_POLICY_ID, and
> other variables.
>
>     This appears to be the last hurdle for compiling /src -- any
quick/easy
> tip on this?  Anyone?
>
>
>
>

Hi,

it is OK that you do not get the error messages when compiling orbcore
because
of the "_core_attr" definition in the beginning of CORBA.h. I got rid of =
the
errors
while compiling by undefining "_core_attr"  when compiling "dynamic", but
wasn=B4t
able to start the poa example dynamically linked because of an initilizat=
ion
error
in omniDynamic300_rtd.dll. So this "solution" seems to help only while
compiling ;-(

Cheers,
Lutz