EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: defining a path of PVA for EPICS base 3.x
From: Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov>
To: matic.pogacnik at cosylab.com, Jong Woo Kim <Jong.Woo.Kim at asu.edu>
Cc: tech-talk at aps.anl.gov
Date: Wed, 4 Mar 2020 20:24:13 -0800
On 3/3/20 11:22 AM, Matic Pogacnik via Tech-talk 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/ )

These websites aren't being updated anymore.  The downloads especially
are all >2 years out of date and should be disregarded.

These old releases contain numerous bugs which have since been fixed.
Users wanting a tar file should start with a 7.0 release tar and take
only the necessary PVA modules.  These constitute a set of versions
which have been tested together.  These directories can be treated
like any other EPICS modules.

modules/pvData
modules/pvAccess
modules/pva2pva
modules/pvaClient
modules/pvDatabase
modules/normativeTypes



> 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)
> 


References:
defining a path of PVA for EPICS base 3.x Jong Woo Kim via Tech-talk
Re: defining a path of PVA for EPICS base 3.x Matic Pogacnik via Tech-talk

Navigate by Date:
Prev: Re: String size limit for Eiger FileWriter when compiling with g++ > 5.2 Bruno Martins via Tech-talk
Next: Re:RE: Asyn support for GPIB-ENET 杨栋亮 via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Re: defining a path of PVA for EPICS base 3.x Johnson, Andrew N. via Tech-talk
Next: areaDetector ADViewers R1-6 released Mark Rivers via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
ANJ, 05 Mar 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·