[omniORB] compiling omniORB3 on NT

[Chung, David]

	David:

	Glad to hear about your progress!  I have several questions, though:

		(1) I am curious as to at exactly what point did your make
fail?  Did you get to genereate omniORB3d.lib, omniORB300_rtd.lib,
omniDymamic3d.lib, or omniDynamic300_rtd.lib?  

		When I run make on your files, the make fails after it
apparently links and generates omniORB3d.lib and omniORB300_rtd.lib.  (It
fails after that point, as it tries to compile irSK.cc in order to generate
omniDynamic3d.lib).

	(2) You referred to extraneous symbols generated.  Let me get this
right -- do you mean that if you compile <top>/src/lib/omniORB2/orbcore and
link it with some CORBA app code, the linker will generate errors because it
finds unresolved symbols?   Or did I misunderstand you?

	(3) is the library generated by running make on
<top>/src/lib/omniORB2/orbcore supposed to be able to successfully link to
CORBA apps without the library generated from
<top>/src/lib/omniORB2/dynamic?  What about the reverse?  (that is, should
the library generated from .../dynamic be able to link to CORBA apps without
the library generated rom .../orbcore?) 

	I would appreciate any (further) info.

> -----Original Message-----
> From:	djr@uk.research.att.com [SMTP:djr@uk.research.att.com]
> Sent:	Saturday, October 16, 1999 9:32 AM
> To:	omniorb-list@uk.research.att.com
> Subject:	Re: [omniORB] compiling omniORB3 on NT
> 
> 
> Hi,
> 
> 
> I've just committed a whole load of changes to the CVS repository to
> support MSVC.  It still isn't quite there yet, but it is a lot closer.  It
> should now compile the runtime libraries (it does for me).  However, I
> still have a link problem.  Just including CORBA.h seems to bring in
> some extraneous references to symbols in the dynamic library.  If anyone
> can find out why these references are generated please let me know.  I
> think it is something to do with sequence templates.
> 
> There may still also be a minor problem with some code generated by the
> idl compiler -- due to a bug in MSVC.  I haven't gotten round to testing
> that thoroughly yet.
> 
> These changes will be available on CVS and in the snapshots after the
> merge tonight.
> 
> 
> Cheers,
> David
>