RE: How do I install to $prefix/EPICS/bin, $prefix/EPICS/lib etc.?

["Davidsaver, Michael" <mdavidsaver@bnl.gov>]

Hello Gary,

The problem is larger than just installing files into standard
locations.  The real difficulty is in patching the EPICS build system to
use a different layout.

When I was considering how to package EPICS for Debian Linux I made the
decision to keep the current layout, but to move the root
'/usr/epics/base', and I am considering changing this to
'/usr/lib/epics' to better follow Debian's rules regarding file system
layout.

Is there a reason you want to rearrange things (aside from the
strangeness of the current arrangement)?

As for installing outside the build directory try:

$ make
$ make INSTALL_LOCATION=/usr/local/epics

Be aware that by default installed binaries are linked with -rpath.


Michael Davidsaver
NSLS2 Controls Group
Brookhaven National Lab


> -----Original Message-----
> From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-
> bounces@aps.anl.gov] On Behalf Of Gary V. Vaughan
> Sent: Thursday, August 05, 2010 2:14 PM
> To: tech-talk@aps.anl.gov
> Subject: How do I install to $prefix/EPICS/bin, $prefix/EPICS/lib
etc.?
> 
> Hi,
> 
> 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:
> 
>   $INSTALL_PREFIX/
>     +-- bin/
>     |    '-- {binaries and scripts go here}
>     +-- db/
>     |    `-- softIocExit.db
>     +-- dbd/
>     |    `-- {dbd files}
>     +-- doc/
>     |    '-- html/
>     |         `-- {html documentation}
>     +-- include/
>     |    `-- {C and C++ header files}
>     +-- lib/
>     |    +-- {compiled libraries}
>     |    `-- perl-5.8.8/
>     |         `-- {perl modules}
>     `-- templates/
>          `-- {template files}
> 
> 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.
> 
> I've got a kludgy workaround that finds lines in the build.log
> file beginning 'g++ -o', and calls the installed libtool script
> to relink targets that match into the install tree structure above
> without leaving references to directories or libraries in the build
> tree in RPATH entries.
> 
> Is there a way to install a runtime EPICS base into the root
> directory using the existing build system?
> 
> Thanks in advance for your help!
> 
> Cheers,
> --
> Gary V. Vaughan (gary@thewrittenword.com)