Subject: |
Re: How do I install to $prefix/EPICS/bin, $prefix/EPICS/lib etc.? |
From: |
Andrew Johnson <[email protected]> |
To: |
[email protected] |
Date: |
Thu, 5 Aug 2010 14:06:06 -0500 |
Hi Gary,
On Thursday 05 August 2010 13:14:04 Gary V. Vaughan wrote:
>
> I am in the process of trying to package EPICS base 3.14.11 into
> native package format on several commercial UNICES, but I can't
> find a nice way to have it install into a standard tree:
The EPICS build system isn't going to work with the standard tree that you've
suggested. EPICS was designed around the ability to cross-compile for other
architectures, which is why we install binaries and libraries into an
architecture-specific subdirectory of <top>/bin and <top>/lib respectively.
How/where are you going to store the EPICS Base libraries cross-compiled for
an RTEMS or vxWorks target? The majority of EPICS sites need to do cross-
builds like that, and your solution is likely to be less interesting to them
if you prevent that by changing the installation structure.
> If I change INSTALL_LOCATION to be anything other than $(TOP)
> then make fails to find any sources to link, and there don't
> appear to be any installation rules to relink the libraries
> and binaries at install time -- nearly all other programs I've
> packaged provide a 'make install' rule for this purpose.
> Is there a way to install a runtime EPICS base into the root
> directory using the existing build system?
You should be able to set INSTALL_LOCATION inside the configure/CONFIG_SITE
file before you build base, pointing it to the top directory where you want it
to make the install tree. This will ensure that the RPATH entries point to
the installation tree. I'm guessing that it might not be possible to set it
to "/" if that's something that you're having problems with, although I'm not
sure why it would break. Note that this also causes the configure directory
to be copied to $(INSTALL_LOCATION); it's needed by application developers to
build IOCs against this installation of Base.
If you want to remove the RPATH entries you're probably better off editing the
configure/os/CONFIG files to remove the options, although you may find you
have to set /etc/ld.so.conf so our build tools like flex and antelope are able
to run. I believe we've added an option to future releases to allow RPATH to
be turned off centrally.
- Andrew
--
The best FOSS code is written to be read by other humans -- Harald Welte
- Replies:
- Re: How do I install to $prefix/EPICS/bin, $prefix/EPICS/lib etc.? David Dudley
- References:
- How do I install to $prefix/EPICS/bin, $prefix/EPICS/lib etc.? Gary V. Vaughan
- Navigate by Date:
- Prev:
VxWorks and Radius Authentication Gary Carr
- Next:
Re: Making a case for cases Purcell, J. David
- 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: How do I install to $prefix/EPICS/bin, $prefix/EPICS/lib etc.? Davidsaver, Michael
- Next:
Re: How do I install to $prefix/EPICS/bin, $prefix/EPICS/lib etc.? David Dudley
- 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
|