Experimental Physics and
Industrial Control System

"J. Lewis Muir" <[email protected]> · Mon, 02 Feb 2015 14:56:00 -0600

On 2/2/15 2:28 PM, Mark S. Engbretson wrote:
> DLL's are standalone entities which have resolved all their library
> reverences at build time. The windows EPICS libs are already
> DLL's. ANYTHING with the correct header files can talk to it - Pascal,
> Fortran, past versions or future versions. All you have to do is find
> out if whatever code that your building apps for can understand the
> DLL and link lib formats.  Grab a recent version for an APS Jenkin
> build and see what happens.  Microsoft is rather compatible with
> itself.
>
> https://jenkins.aps.anl.gov/job/epics-base-3.14/
> https://jenkins.aps.anl.gov/job/epics-base-3.15/

Hi, Mark.

Thanks for your reply.  That's an interesting suggestion.  I didn't know
the DLLs were available anywhere.  My library is written in C, so there
may be some possibilities that could work if I just used the DLLs from
Jenkins.

Maybe you know, or maybe a question for Andrew: do those Jenkins builds
include the Known Problems patches?  I would bet they do, but I'm not
certain.

> That being said - nothing keeps you from building those apps against
> a 15 year version of epics. You just don't get later features such
> as large arrays.  Do you need anything that only exists in current
> versions?

I do happen to need large arrays, but even if I didn't, I like the
latest 3.14 version because it includes all bug fixes to date.  I
definitely don't want to try using some old version and pull my hair out
trying to figure out some insane problem only to discover that the cause
is a bug that's been fixed for years!

Regards,

Lewis

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System