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
