[omniORB] Re: Windows NT and dllimport/dllexport

[John A. Byerly]

Thanks for the response.

I figured out the names of the macros.

In our environment, steps 1a and 1b don't apply (we don't have any dynamic
skeletons).  I was able to figure out what was being accomplished in step 1c
(introducing gnumake to our team would not be advisable) and created a .DEF
file by hand.  I performed step 2.

That fixed the problem.

Many thanks!

JAB

> -----Original Message-----
> From: sll@uk.research.att.com
> [mailto:sll@uk.research.att.com]On Behalf
> Of Sai-Lai Lo
> Sent: Friday, August 04, 2000 10:46 AM
> To: John A. Byerly
> Cc: omniorb-list@uk.research.att.com
> Subject: Re: [omniORB] Re: Windows NT and dllimport/dllexport
>
>
> Sigh! I got the macro names wrong. Should be:
>
> USE_dyn_stub_in_nt_dll, USE_core_stub_in_nt_dll and
> USE_stub_in_nt_dll.
>
> Sai-Lai
>
> >>>>> Sai-Lai Lo writes:
>
> > I like to know more about your problem.
> > Firstly, let me explain the recommended steps to compile
> and use the stubs
> > in DLLs:
>
> > 1. To compile:
> >      a) *SK.cc stub files,
> >            Specify the CPP flag -DUse_dyn_stub_in_nt_dll
> >                                  ^^^^^^^^^^^^^^^^^^^^^^^
> >                                  This put dllimport on the
> relevant symbols
> >                                  exported by *DynSK.cc files.
>
> >      b) *DynSK.cc stub files,
> >            Specify the CPP flag -DUse_core_stub_in_nt_dll
>
>
> --
> Sai-Lai Lo                                   S.Lo@uk.research.att.com
> AT&T Laboratories Cambridge           WWW:
> http://www.uk.research.att.com
> 24a Trumpington Street                Tel:   +44 1223 343000
> Cambridge CB2 1QA                     Fax:   +44 1223 313542
> ENGLAND
>
>