Experimental Physics and Industrial Control System
|
Dear Core-Talkers,
For a device support partly written in C++, we have been getting a pull request for Windows builds that adds extern "C" declarations around EPICS exports, e.g.
-epicsExportAddress(double, connectInterval); + epicsExportAddress(double, connectInterval);
with the comment
I am afraid that the extern statements in epicsExport.h are ignored by VS compiler when expanding the epicsRegisterFunction macro. Therefore they need to be repeated here otherwise we get a linking failure when building test IOC.
As my Windows experience is very limited - is there a better way to handle that?
Thanks, ~Ralph
- Replies:
- RE: epicsExport.h on Windows Mark Rivers
- Re: epicsExport.h on Windows Michael Davidsaver
- Navigate by Date:
- Prev:
Re: Concerns about link-support-2 branch Andrew Johnson
- Next:
RE: epicsExport.h on Windows Mark Rivers
- Index:
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:
Jenkins build is back to normal : epics-base-3.16-mac-test #71 APS Jenkins
- Next:
RE: epicsExport.h on Windows Mark Rivers
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 21 Dec 2017 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|