Re: defining a path of PVA for EPICS base 3.x

["Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov>]

If you’re willing to upgrade to EPICS 7 recent versions of the PVA modules included with it are significantly more robust and reliable than the stand-alone versions that worked with Base 3.x, and there’s less work setting them up. I would recommend upgrading, especially for recent AreaDetector versions (which might not build with the older V4 code anyway).

- Andrew

On Mar 3, 2020, at 1:22 PM, Matic Pogacnik via Tech-talk <tech-talk at aps.anl.gov> wrote:

Hi,

EPICS V3 doesn’t include V4 modules. They must be downloaded separately from http://epics-pvdata.sourceforge.net/index.html (https://sourceforge.net/projects/epics-pvdata/files/ )

Best regards,
Matic


----- Original Message -----
From: "Jong Woo Kim via Tech-talk" <tech-talk at aps.anl.gov>
To: tech-talk at aps.anl.gov
Sent: Tuesday, March 3, 2020 7:57:03 PM
Subject: defining a path of PVA for EPICS base 3.x

Hi,

I am using the following versions.

EPICS base-3.15.6
asyn4-37
areaDetector-R3-9
ADCore-R3-9

There is a way to define the path of 'PVA' for those who use prior to EPICS base 7.
The following shows an example for EPICS V4. I couldn't find a corresponding folder or files in EPICS base-3.15.6.
Do I have to upgrade?
_________________________________________________________________________
# If CONFIG_SITE.local defines WITH_PVA=YES and EPICS_BASE is prior to 7.0 then define the path here
# If using EPICS_BASE 7.0 or later the PVA files are in base itself and no additional definitions are needed.
#PVA=/corvette/usr/local/epics-devel/epicsV4/EPICS-CPP-4.6.0
# PVA modules
# For versions prior to EPICS base 7.0 use this
#PVCOMMON=$(PVA)/pvCommonCPP
#PVACCESS=$(PVA)/pvAccessCPP
#PVDATA=$(PVA)/pvDataCPP
#PVDATABASE=$(PVA)/pvDatabaseCPP
#NORMATIVETYPES=$(PVA)/normativeTypesCPP
-include $(AREA_DETECTOR)/configure/RELEASE_LIBS.local.$(EPICS_HOST_ARCH)

-- 

Complexity comes for free, Simplicity you have to work for.