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  2013  2014  2015  2016  2017  <20182019  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  <20182019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Purpose of INSTALL_LOCATION Variable
From: Michael Davidsaver via Tech-talk <[email protected]>
To: Abdalla Ahmad <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Sun, 25 Nov 2018 07:59:48 -0800
On 11/25/18 12:05 AM, Abdalla Ahmad via Tech-talk wrote:
> Hi
> 
>  
> 
> As you know this variable is defined in configure/CONFIG_SITE (or CONFIG_APP in some exceptions) and quoting from that file, this variable is used "To install files into a location other than $(TOP)".
> 
> 1.       What files are being installed?

Everything which would be copied to eg $(TOP)/bin and similar (lib, db, dbd, ...).

> 2.       Defining this variable in EPICS base does not include the startup folder scripts, therefore anything using the "installed" EPICS_BASE will not find the script EpicsHostArch for example. Is this an issue or this is how it works?

While there have been recent changes in Base 7.0.x, this was long the case.
For the Debian packages, I handled these specially.

https://github.com/epicsdeb/epics-base/blob/5e0e68dfc6c2cdd700aef15b65fdd0068c7e00f7/debian/epics-dev.install#L28-L30

> 3.       Base on #1, when you define INSTALL_LOCATION in some modules that have UI files or some databases in App/Db/, why these files are not included in the installation?

Some modules are lack about installing from Db/.  These need to be listed
in *App/Db/Makefile.  Probably worth mentioning to the module author,
though in the short term this means additional work in the packaging.


Also, you'll want to look at FINAL_LOCATION, and maybe LINKER_USE_RPATH as well.


> Best Regards,
> 
>  
> 
> Abdalla Ahmad
> 
> Control Engineer
> 
> SESAME
> 
> Allan, Jordan.
> 
> Tel: (+962-5) 3511348 , ext. 265
> 
> Fax: (+962-5) 3511423
> 
> Mob: (+962-7)88183296
> 
> www.sesame.org.jo <http://www.sesame.org.jo/>
> 
>  
> 


References:
Purpose of INSTALL_LOCATION Variable Abdalla Ahmad via Tech-talk

Navigate by Date:
Prev: Purpose of INSTALL_LOCATION Variable Abdalla Ahmad via Tech-talk
Next: Re: Packaging EPICS and support modules as RPM Michael Davidsaver via Tech-talk
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  <20182019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Purpose of INSTALL_LOCATION Variable Abdalla Ahmad via Tech-talk
Next: Melbourne EPICS Collaboration Meeting Slides [SEC=UNCLASSIFIED] POZAR, Andraz via Tech-talk
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  <20182019  2020  2021  2022  2023  2024 
ANJ, 26 Nov 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·