Hi Juan,
> The problem is because of the following
> definition in my RELEASE file (we need to install in a different
> location relative to TOP):
>
> INSTALL_LOCATION_APP=$(TOP)/../install
>
> Apparently Release.pm does not like $(TOP) in the INSTALL_LOCATION_APP
> variable. All the other support modules we are using (asyn, sncseq,
> modbus) have a similar definition and Release.pm does not complain. Do
> you know why waveProc is somewhat different to asyn or sncseq?
You're not supposed to use $(TOP) at all in a RELEASE file; RELEASE is special in the EPICS build system and should not be used for setting any variables other than pointers to other support applications. The right place to set other variables is in the module's configure/CONFIG_SITE file instead (or the related architecture-specific files).
The waveProc application hasn't been updated in a while and might have some rather old versions of the configure/* files, so you might want to try replacing everything in its configure directory with the contents of <base>/templates/makeBaseApp/top/configure instead (especially if the comments in the existing files contradict what I've written above).
HTH,
- Andrew
- Replies:
- Re: Error compiling waveProc1-0 on base 3.14.12 Juan.Guzman
- References:
- Re: Error compiling waveProc1-0 on base 3.14.12 Juan.Guzman
- Navigate by Date:
- Prev:
Re: Error compiling waveProc1-0 on base 3.14.12 Juan.Guzman
- Next:
APS Network Maintenance after December 26th Andrew Johnson
- 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
- Navigate by Thread:
- Prev:
Re: Error compiling waveProc1-0 on base 3.14.12 Juan.Guzman
- Next:
Re: Error compiling waveProc1-0 on base 3.14.12 Juan.Guzman
- 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
|