Experimental Physics and
Industrial Control System

Hi Andrew,

should I start over with 3.15.6? - I started with 3.15.5 some
time earlier this year because it was labeled as the latest
stable release (little did I know that a bunch of other upgrades
in other areas would take a lot longer than anticipated - you
know how these things go).

Thanks,
Maren

On 10/10/18 10:43, Johnson, Andrew N. wrote:

Hi Maren,

If your system configuration files were setting EPICS_HOST_ARCH there should have been no need to copy anything manually to the install tree ever since we added the INSTALL_LOCATION setting to the Base/configure/CONFIG_SITE file. Unfortunately here at APS I don't have to set EPICS_HOST_ARCH and I rarely tested the use of INSTALL_LOCATION so I didn’t realize that the build system would try to execute the EpicsHostArch.pl script from the startup directory in that specific circumstance.

The idea of the startup changes that are in 3.15.6 (and 3.14.12.8) is to fix this problem. We now install and run the EpicsHostArch.pl script to/from the $(EPICS_BASE)/lib/perl directory if necessary, and the startup directory is not required in the install tree.

If you find you still have to copy stuff out of the source tree after building Base with INSTALL_LOCATION set I want to know about it.

- Andrew

On Oct 10, 2018, at 3:18 PM, Maren Purves <[email protected]> wrote:

On 10/10/18 04:30, Lucock, Richard M wrote:

Hi,

    If $(TOP) is not equal to $(INSTALL_LOCATION), you cannot see startup
directory in 3.15.5 and 7.0.1.1. From our environment, we create that
directory, and copy EpicsHostArch.pl file into it.

    From 3.15.6-rc1, EpicsHostArch will be in startup directory if $(TOP)
is equal to $(INSTALL_LOCATION). However, if $(TOP) is not equal to
$(INSTALL_LOCATION), we cannot see "startup" path in
$(INSTALL_LOCATION). However, EpicsHostArch.pl file will be copied into
$(EPICS_BASE)/lib/perl path.

   Thanks for that, at least I know I'm not doing something wrong.

I partially circumvented this by copying a lot of stuff from the
source tree to the install tree. For as long as I have used EPICS
we have always had separate source trees and install trees and I'm
not willing to abandon that concept - we do that for the rest of
our software as well.
At some point in the extensions I got stuck - and then side-tracked
into other stuff that also needed to be done.

I hope to get back to that soon-ish (upgrading from 3.13.8) and I
hope that there are others struggling with the same concept and
maybe having come up with other solutions. I do not consider
installing into the source tree a solution.

Maren

Replies:

Re: Questions about install Johnson, Andrew N.

References:

Questions about install Lucock, Richard M

Re: Questions about install Jeong Han Lee

Re: Questions about install Lucock, Richard M

Re: Questions about install Maren Purves

Re: Questions about install Johnson, Andrew N.

Navigate by Date:

Prev: Re: Questions about install Johnson, Andrew N.

Next: Re: Questions about install Michael Davidsaver

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: Questions about install Johnson, Andrew N.

Next: Re: Questions about install Johnson, Andrew N.

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