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
- Replies:
- RE: CA Gateway 2.0.5.0 released freddie.akeroyd
- References:
- CA Gateway 2.0.5.0 released Ralph Lange
- RE: CA Gateway 2.0.5.0 released freddie.akeroyd
- Navigate by Date:
- Prev:
RE: CA Gateway 2.0.5.0 released freddie.akeroyd
- Next:
pyepics "Virtual circuit disconnect" CA.Client.Exception Walter Werner
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: CA Gateway 2.0.5.0 released freddie.akeroyd
- Next:
RE: CA Gateway 2.0.5.0 released freddie.akeroyd
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|