This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: help in installing binaries in both /bin and /usr/bin
- From: Alexandre Duret-Lutz <duret_g at lrde dot epita dot fr>
- To: "Aneesh Kumar K.V" <aneesh dot kumar at digital dot com>
- Cc: automake at gnu dot org
- Date: Wed, 08 Jan 2003 12:06:32 +0100
- Subject: Re: help in installing binaries in both /bin and /usr/bin
- References: <1041865607.27821.16.camel@satan.xko.dec.com>
>>> "Aneesh" == Aneesh Kumar K V <aneesh.kumar@digital.com> writes:
Aneesh> Hello,
Aneesh> I want to write Makefile.am that need to install
Aneesh> binaries in both /bin and /usr/bin.
`bin_PROGRAMS = foo' installs foo in `${bindir}'.
`barexec_PROGRAMS = baz' installs baz in `${barexecdir}'.
If you need more directories you can invent them, just defines
as many *dir variables as you need (in Makefile.am or using
AC_SUBST in configure.ac).
[...]
Aneesh> As of now i have
Aneesh> bin_PROGRAMS=abc
Aneesh> bin_PROGRAMS=xyz ==> What do i assign this to in order to
Aneesh> install it in /usr/bin
One possibility among many variations:
bin_PROGRAMS = abc
usrbinexecdir = $(exec_prefix)/usr/bin
usrbinexec_PROGRAMS = xyz
This is assuming $(exec_prefix) gets empty in some way, so abc
installs in /bin as it seems you want.
Using $(exec_prefix) to defines $(usrbinexecdir) makes sure the
user still gets the expected result with `make prefix=/tmpdir
install'. Using `exec' in the name of the `usrbinexecdir' variable
ensures `xyz' will be installed by `install-exec', not `install-data'.
--
Alexandre Duret-Lutz