Re: [omniORB] omniORB client to ORBit server

[Duncan Grisby <duncan grisby org>]

On Thursday 6 November, baileyk@schneider.com wrote:

> http://www.omniorb-support.com/pipermail/omniorb-list/2003-October/024387.html
> 
> which is a post I made recently on building a DLL from omniORB stubs.  Of
> course you will still need to give your customer your IDL, or equivalent
> documentation of your interfaces.  The generated header files are not the
> best form of documentation for your DLLs.

That is true if you want to package up _just_ the output from the IDL
compiler into a DLL. However, if what you want to do is package up the
client code itself, as well as the generated stubs, into a single DLL,
there is no need for any of that. You just link the stub sources into
your DLL and it will all work fine.

What do you actually want to have in your DLL?

> http://www.omniorb-support.com/pipermail/omniorb-list/2003-October/024392.html
> 
> which clarifies some details.

To answer some of the questions raised by that, I should explain the
purpose of the _OMNIORB_NTDLL_IMPORT macro. If you just build a DLL on
Windows, no symbols at all are exported from it. The omniORB build
process creates a .def file that causes (almost) everything to be
exported from it.

When using a DLL, exported functions are used automatically. However,
exported static data is not. That is the purpose of the
_OMNIORB_NTDLL_IMPORT macro. It marks those bits of static data that
must be available to importers of the DLL.

Cheers,

Duncan.

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