![]() |
![]() ![]()
Experimental Physics and
| ||||||||||||||||
|
Hi Eusebio, On Wed, 20 Dec 2023 at 08:53, Eusebio Naif Al-Soliman Fuentes <eunaif at correo.ugr.es> wrote:
I'm not sure I understand what you mean. If you are referring to the OPC UA Device Support, you can use the binary distribution if you don't want to or can't compile the low-level client library. When you use the binary distribution, you don't need to download/compile the Device Support module nor the low-level client library, as both are part of the binary distribution.
That question does not really make sense. EPICS Base contains some libraries and configuration files. Additional EPICS support modules contain more libraries and configuration files. To create an IOC that uses things from support modules, you need both EPICS Base and the support modules. The IOC binary needs to be linked against the libraries from the support modules and EPICS Base. Configuration files from the support modules and EPICS Base are used to create the configuration files for the IOC. EPICS relies on PV names to be unique in the system. Running multiple IOCs with the same PVs is an error. Clients will connect to one or another quasi-randomly and spit out error messages.
Any EPICS build (when you run "make" inside an EPICS module) will look for RELEASE.local files in different places, including in the directory above its TOP and inside the TOP/configure directory. If you don't want to repeat the configuration inside every support module, putting a single file one level above the modules is read by all of them. RELEASE and RELEASE.local files contain (that's documented) the locations of all support modules as multiple lines of the form MODULE_NAME = /absolute/path/to/the/module with the EPICS_BASE definition usually last. Cheers, ~Ralph
| ||||||||||||||||
ANJ, 20 Dec 2023 |
![]() · Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |