Re: How to use registry to replace vxWorks symLib?

[Michael Westfall <mwestfal@gemini.edu>]

Hi Andrew,

We are in fact wanting to port the vmi5588 driver to EPICS OSI compliance, so that it can run on an RTEMS IOC.

Since you wrote that driver originally, maybe you have some idea as to how to proceed?

Thanks,

On Wed, Apr 20, 2016 at 1:18 PM, Andrew Johnson <anj@aps.anl.gov> wrote:

Hi Mike,

On 04/20/2016 09:05 AM, Michael Westfall wrote:
> Is there a tutorial or example somewhere that could help me understand
> how to convert a driver to use the EPICS registry in place of the
> vxWorks symLib?

Can you give a bit more information about what symbols this driver is
looking up?

The EPICS registry isn't really a general-purpose symbol table, any
symbol that needs to be found using it must first have been registered,
usually in a C++ static constructor. It is possible to add your own
symbol types if you need that (see registry.h; a registryID is just any
pointer which must be the same for both registration and lookup).

You might want to take a look at the epicsFindSymbol.h API in libCom
which provides a generic API to any underlying OS symbol table; this
might be sufficient for your purposes, although some OSs might not be
able to support it (implementations are provided for VxWorks, Linux,
solaris, Darwin and Windows).

HTH,

- Andrew

--
There are only two hard problems in distributed systems:
  2. Exactly-once delivery
  1. Guaranteed order of messages
  2. Exactly-once delivery
 -- Mathias Verraes

--

Mike Westfall

Control Systems Software Engineer