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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Questions about install |
From: | Jeong Han Lee <[email protected]> |
To: | [email protected] |
Date: | Wed, 10 Oct 2018 16:19:21 +0200 |
Hi Richard,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. HTH, Han On 10/10/18 4:12 PM, Lucock, Richard M wrote:
Hi, I have just built base-3.15.5, with INSTALL_LOCATION in config/CONFIG_SITE set to a different directory than my source directory (call it /path/base). That is the only change that I made to the epics files before running make. I then tried to build a test application (that is known to work), having set EPICS_BASE in configure/RELEASE to /path/base. The build failed, because it couldn't find the startup directory. There is a startup directory in source directory, but nothing got created in my install location. Copying the startup directory from source to install by hand fixed the problem, and the test app ran. I am unsure what I might have done wrong when building the epics installation. Any suggestions ? (I am working on a linux platform). Thanks, Richard