Experimental Physics and
Industrial Control System

On Fri, 7 Sep 2012 10:38:22 +0400
Pavel Masloff <[email protected]> wrote:

> Hey Angus,
> 
> I prefer absolute paths to relative, so I have got the following structure
> and I always give a full path to epics_base in RELEASE:
> 
> /opt/epics/
>            apps
>            base
>            modules
>            extensions

Hi Pavel,

Thanks for showing your setup. Even though our deployment structure
looks exactly like this, I didn't want to go that way so as to support
developing from multiple working copies.

For instance, on my workstation I currently have both a feature branch
(upgrading base, asyn & some other components) and the current deployed
branch that runs on the accelerator.

If the paths were hard-coded, I'd have to switch the same directory
between branches (and commit any outstanding changes) any time I needed
to make a change or a test in the opposing branch.

- Angus

References:

EPICS build system, RELEASE file, and relative paths Angus Gratton

Re: EPICS build system, RELEASE file, and relative paths Pavel Masloff

Navigate by Date:

Prev: Re: EPICS build system, RELEASE file, and relative paths Pavel Masloff

Next: Re: Epics driver using BLT or CBLT to read FIFO wanted 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 

Navigate by Thread:

Prev: Re: EPICS build system, RELEASE file, and relative paths Pavel Masloff

Next: RE: EPICS build system, RELEASE file, and relative paths Mark Rivers

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