Experimental Physics and
Industrial Control System

<[email protected]> · Fri, 12 Dec 2014 17:28:26 +0000

Hi Andrew,

the functions are marked with both epicsShareFunc and  epicsShareAPI in the caPutLog header files, but the epicsShareAPI was missing from the *.c files and so there was a mismatch between   __stdcall and __cdecl declarations. I just added epicsShareAPI to the *.c to make them consistent with the *.h, but removing epicsShareAPI from the *.h instead would work equally well. I've no particular need for epicsShareAPI myself.

Regards,

Freddie

> -----Original Message-----
> From: Andrew Johnson [mailto:[email protected]]
> Sent: 12 December 2014 16:22
> To: Akeroyd, Freddie (STFC,RAL,ISIS); [email protected]; tech-
> [email protected]
> Subject: Re: CA Gateway 2.0.5.0 released
> 
> Hi Freddie,
> 
> On 12/12/2014 09:26 AM, [email protected] wrote:
> > I've compiled 2_0_5_0 both with and without the caPutLog support on
> > windows 7 x64, but have only checked the non-caPutLog version so far
> > at runtime.  I enclose the small changes that were required to the
> > caPutLog and gateway code to build it, I hope to try the caPutLog
> > support in the near future.
> 
> Do you really need to change the calling conventions for those
> functions? The epicsShareApi macro expands to __stdcall which makes the
> generated code use Pascal calling conventions instead of the C ones. I
> suspect you meant to mark them with epicsShareFunc instead, which
> expands to the appropriate __declspec(dll*port) attribute.
> 
> I have been trying to remove the use of epicsShareApi from the EPICS
> APIs in the last few years, is there some reason to reverse that?
> 
> - Andrew
> --
> People everywhere confuse what they read in newspapers with news.
> -- A. J. Liebling

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System