EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  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  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Why is RELEASE now included in CONFIG_INSTALLS ?
From: "Brian McAllister" <[email protected]>
To: [email protected]
Date: Thu, 13 Jun 2013 14:43:29 -0400
Hello EPICS folks -

I have returned to EPICS work after some time and encountered some
unexpected behavior.

The last version I worked with was 3.14.8.2.  Sometime between that release
and 3.14.12.3, the definition of "CONFIG_INSTALLS" in
base/configure/CONFIG_COMMON was changed to include "RELEASE*".  I say
"sometime" as this change is NOT DOCUMENTED in the release notes.

I was using a directory structure for modules such as Asyn and StreamDevice
where I defined INSTALL_LOCATION as the parent directory of all the module
directory trees so that all the includes/libs/dbds from all the modules
were in one location, simplifying the inclusion of such modules in IOC
applications.  This also allowed me to "make" all the modules at once from
the parent directory.

Now, the standard build system wants to install the RELEASE file from each
module tree into to the top-level "configure" directory, where they
over-write each other.

Before I hack the config files to do what I want, I'd like to understand
the purpose of this change.  There was a reason, right ?

----
Brian McAllister                                   Senior Software Engineer
[email protected]                                                Bates Lab
(617) 253-9537                                                Middleton, MA

Replies:
Re: Why is RELEASE now included in CONFIG_INSTALLS ? Andrew Johnson

Navigate by Date:
Prev: Re: SEQ keep PV value during seq-init [SOLVED] Fabian S.
Next: calc DTYP Pearson, Matthew R.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: LAN GPIB Anthony Pietryla
Next: Re: Why is RELEASE now included in CONFIG_INSTALLS ? Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·