EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  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  <20032004  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: "Billy R. Adams" <[email protected]>
To: Geoff Savage <[email protected]>
Cc: "'[email protected]'" <[email protected]>
Date: Fri, 07 Nov 2003 15:55:57 -0500
Geoff,

I will only address the path issue, but not EPICS.

Using "sh" shell commands:

Example 1.
An absolute path (example: "/usr/local/epics/bin") is specifically defined and works.


Example 2.
     Also the following will work:
set EPICS_DIR = /usr/local/epics
set BIN_DIR = /bin
set $PATH = $EPICS_DIR$BIN_DIR
     then:
> echo $PATH
/usr/local/epic/bin

    So if you used $PATH, you would also get to
/usr/local/epics/bin .

Example 3.
   Now if you add an external product (say in /usr/local/product/bin)
then you could:
set $PRODUCT_DIR =  $EPICS_DIR$/../product/bin
and
> echo $PRODUCT_DIR
/usr/local/epics/../product

   /usr/local/epics/../product is equal to /usr/local/product and would
work.  But, there is more chance of error.
   Just specifying set $PRODUCT_DIR = /usr/local/product reduces the
chances of making an error, especially when referencing a location
outside of your current location, in this case EPICS.

    If this seems confusing, then maybe that was my point.  Use the
simplest way that works.

Hope this helps.

Billy Adams

Geoff Savage wrote:
Hi,

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)

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?

I'm using epics R3.14.4 on solaris-sparc.

Thanks

Geoff





-- Billy Adams <mailto:[email protected]> Raytheon Technical Services Assigned to: Research Facilities Branch of Research Facilities Management Office 16 Victory Street Mail Stop 413 Building 1251, Room 126D NASA Langley Research Center Hampton, Va. 23681-2199 Phone 1-757-864-6242 Fax 1-757-864-8095



References:
configure/RELEASE contents Geoff Savage

Navigate by Date:
Prev: configure/RELEASE contents Geoff Savage
Next: building et_wish on HP-UX Bill Cruise
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: configure/RELEASE contents Geoff Savage
Next: Re: configure/RELEASE contents Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  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 ·