EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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  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 
<== Date ==> <== Thread ==>
Subject: Re: configure/RELEASE contents
From: Andrew Johnson <[email protected]>
To: Geoff Savage <[email protected]>
Cc: "'[email protected]'" <[email protected]>
Date: Fri, 07 Nov 2003 18:55:49 -0600
Geoff Savage wrote: 

I have two environment variables that are set when I go to build a top
area, EPICS_DIR and EPICS_EXTENSIONS_DIR, in addition to
EPICS_HOST_ARCH.  I want to use these environment variables in
configure/RELEASE to specify where the external products are located.

EPICS_BASE=$(EPICS_DIR)
SYMB=$(EPICS_EXTENSIONS_DIR)
VXSTATS=$(EPICS_EXTENSIONS_DIR)

We semi-deliberately don't look at environment variables used in the RELEASE, because that's asking for an unmanagable build system - you can't be sure that you'll ever be able to build exactly the same binary that you were running two versions ago because you don't know how the guy who built it had his environment variables set (unless you put the environment variables under configuration control as well).

With these definitions there are environment variables missing from
configure/O.solaris-sparc/CONFIG_APP_INCLUDE.  For example when
constructing dbd files that include dbCommon.dbd the dbCommon.dbd file
is not found.

When I use absolute paths everything works.  Would someone please remind
me why I need to use absolute paths when specifying products in the
configure/RELEASE file?  Can I specify these variables in a different
location?

Don't use environment variables. Your configure/RELEASE file can contain include statements, so can pull in settings from files elsewhere. I suggest that if you don't like having to set up all your pointers to the 'right' versions in every application, that you have another file containing
SUPPORT=/path/to/something
EPICS_DIR=/path/to/base
SYMB=$(SUPPORT)/symb
VXSTATS=$(SUPPORT)/vxStats

Now if you want to change the version of symb used in everything, you can just modify that one file.

- Andrew
--
There are 10 types of people in the world:
Those who understand binary, and those who don't.

Replies:
Re: configure/RELEASE contents Benjamin Franksen
References:
configure/RELEASE contents Geoff Savage
Navigate by Date:
Prev: Re: configure/RELEASE contents Benjamin Franksen
Next: Re: a question about rup in sad Kazuro FURUKAWA
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: configure/RELEASE contents Benjamin Franksen
Next: Re: configure/RELEASE contents Benjamin Franksen
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 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·