Microsoft managed code CLI C++ and EPICS

[Mark Clift <Mark.Clift@synchrotron.org.au>]

Hi Mark, 

Thanks for your reply.  A change of requirements means that I no longer need to solve the problem of mixing EPICS, and managed code.  I did learn a few things that maybe helpful though.  With regard to the interop facility only.  I believe the /clr (common language runtime) must be applied to use interop.

1.  EPICS base 3.14.12-2 will compile and run as normal with the following setup

Line 297 CONFIG.win32-x86.win32-x86

CCC = cl /nologo /EHa /GR /clr

Note change in exception type, and addition of /clr flags.  (ie. /EHsc and /clr are not compatible)

Other build settings:

SHARED_LIBRARIES=YES
STATIC_BUILD=NO

Required as /clr is not compatible with static builds (ie.  /clr and /MT are not compatible)

2.  Cannot get Asyn 4-20 to build dynamically due to epicsShareFunc in paramVal.cpp/.h

So it seems possible solutions are:

1.  Make Asyn 4-20 compatible with dynamic builds on windows.
2.  Change over to the COMwrapper approach.  I have example code on this process which is standard c++ calling managed code via a COMwrapper dll.  The trick is to use C# for the wrapper dll.  For C++ it seems there is little help available to develop COMwrapper dlls.

Option 1 sounds reasonably elegant, option 2 not so much.

Cheers,

Dr. Mark Clift
Senior Controls Engineer
Australian Synchrotron
800 Blackburn Road
Clayton 3168
Ph: +613 8540 4264
Fax: +613 8540 4200
Mail: Mark.Clift@Synchrotron.org.au