>
> > 1) The EPICS startup script will add the following directories to
> > a user's path (for application development)
> >
> > ./base/bin/$HOST_ARCH
> > ./base/tools
> > /usr/local/epics/extensions/bin/$HOST_ARCH
>
> I'm not fond of installing code in /usr/local. Assume that EPICS is installed
> in the path $EPICS, then add the following to everyone's path:
>
> $EPICS/base/bin/$HOST_ARCH
> $EPICS/base/tools
> $EPICS/extensions/bin/$HOST_ARCH
>
> At CEBAF we have a "setup" utility that lets us type
>
> setup epics3_12
>
> and setup finds and sources a .setup file in the directory
But doesnt this mean that everytime an application developer
changes to a new application directory he/she has to make sure it is on the
same release or else has to type "setup epics3_12".
The APS developed S/R system was designed so that users never had to
think about these things. By placing things in /usr/local/epics and
having soft links for things like base in app directories users always
automatically get the correct things.
By the way there is no necessity that path be in /usr/local/epics.
It only needs a site specific standard place.
Marty Kraimer
- Replies:
- Re: Building for more than one host architecture watson
- Navigate by Date:
- Prev:
Re: Building for more than one host architecture winans
- Next:
Re: Building for more than one host architecture watson
- 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: Building for more than one host architecture watson
- Next:
Re: Building for more than one host architecture watson
- 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
|