[omniORB] MS VC++ 6.0 // unresolved links

[Ameya Virkar]

Hello James, 

Few months back, I had experienced a similar issue (it was actually memory
leak). I requested omniORB users to send me a sample VC++ Workspace file.
After using the sample Workspace file, I was able to solve my problem. Maybe
you can also do the same. Here's the link to the workspace file

http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20040130/1
a84ac79/client-0002.obj 

You can get details by browsing the discussion thread at:
http://www.omniorb-support.com/pipermail/omniorb-list/2004-January/024942.ht
ml 

Regards,
Ameya Virkar
Singapore Technologies Electronics


-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Mike Mascari
Sent: Wednesday, June 16, 2004 11:30 PM
To: James E Taylor
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] MS VC++ 6.0 // unresolved links

James E Taylor wrote:

> They're all set.  This is the full list of compilation options:
> 
> /nologo /MD /W3 /Gm /GX /ZI /Od /D "_DEBUG" /D "WIN32" /D
> "_CONSOLE" /D "_MBCS" /D "__WIN32__" /D "__x86__" /D
> _WIN32_WINNT=0x0400 /D "__NT__" /D __OSVERSION__=4 /FR"Debug/"
> /Fo"Debug/" /Fd"Debug/" /FD /GZ 

Here is what I use for a debug build:

1) Compile flags:

/nologo /MDd /W3 /Gm /GX /ZI /Od /I "./" /D "WIN32" /D "_DEBUG" /D 
"_WINDOWS" /D "_AFXDLL" /D "_MBCS" /D "__WIN32__" /D "__x86__" /D 
"__NT__" /D __OSVERSION__=4 /Fp"Debug/example.pch" /Yu"stdafx.h" 
/Fo"Debug/" /Fd"Debug/" /FD /GZ /Zm200 /c

2) Link flags:

wsock32.lib advapi32.lib omniORB403_rtd.lib omniDynamic403_rtd.lib 
omnithread30_rtd.lib omnisslTP40_rtd.lib

3) Link directories:

<amongst others>

C:\Program Files\omni\lib\x86_win32

Of course, linking omnisslTP40_rtd.lib is optional, if you want SSL 
support. I'm not sure, but it might be possible that the /MD switch 
instead of the /MDd switch is the problem. Also, the above is for a 
Win32 application, not a console application, but I doubt that would 
affect linking in omniORB libraries...

HTH,

Mike Mascari


_______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list