| 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 2020 2021 2022 2023 2024 2025 | 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 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: compilation error on pvData wrt epics base |
| From: | Jeong Han Lee <[email protected]> |
| To: | "Johnson, Andrew N." <[email protected]> |
| Cc: | EPICS Tech Talk <[email protected]> |
| Date: | Sat, 23 Jun 2018 23:13:46 +0200 |
Hi Andrew, My BASE is in the following location: $ tree -L 1 /epics/base-3.16.1/ /epics/base-3.16.1/ ├── [root 4.0K] bin ├── [root 4.0K] configure ├── [root 4.0K] db ├── [root 4.0K] dbd ├── [root 4.0K] html ├── [root 12K] include ├── [root 4.0K] lib ├── [root 4.0K] startup └── [root 4.0K] templates And I added the RELEASE.local in pvDataCPP/configure with EPICS_BASE=/epics/base-3.16.1/I am using base-3.15.5 and 3.16.1, I don't need EPICS_LIBCOM variable in RELEASE, so I add only EPICS_BASE. That is only what I add into pvDataCPP.
Do I miss something? Best, Han On 06/23/2018 07:22 PM, Johnson, Andrew N. wrote:
Hi Han When you wrote “install pvData (in source directory)” what did you mean, and did you edit the pvData/configure/RELEASE file? I suspect you are not configuring the pvData module correctly. Unless you’re using EPICS 7 or the fully bundled 4.7 release you need to treat each of the PVA modules as a regular support module, installing them in their own area and editing the configure/RELEASE files as appropriate (there should be comments in each file explaining what other modules they need to point to). It is also possible to set a value for INSTALL_LOCATION to a common directory in the modules’ CONFIG_SITE file, in which case you don’t have to worry about editing the RELEASE files. - Andrew