From: Karel Zak <kzak@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Add rulesdir to libudev.pc
Date: Thu, 15 Jan 2009 22:59:51 +0000 [thread overview]
Message-ID: <20090115225951.GC7646@nb.net.home> (raw)
In-Reply-To: <1231444183.5298.24.camel@californication>
On Thu, Jan 08, 2009 at 10:43:13PM +0100, Kay Sievers wrote:
> Maybe we should drop that exec_prefix use und invent --slibdir (s like
> in --(s)bindir), which other projects think about to introduce, and we
> would require: --prefix, --libdir=, --slibdir=, --sbindir> --sysconf-dir to be specified at configure time? Maybe that's easier
> to handle, I was just waiting what the glib guys plan to use, because
> they have similar problems with configure specifying the rootfs as
> install location.
My $0.02... util-linux-ng installs files "everywhere" (/sbin,
/bin, /usr/bin, /usr/sbin, /etc, ...)
The build system differentiate between $bindir and $usrbinexec, ...
etc.
The important is that the default $exec_prefix (/usr) means "default
locations" -- so /{bin,sbin,etc} for rootfs stuff and /usr/bin for
/usr stuff. I think you can use the same logic for /lib and /usr/lib.
We follow autotools and we don't modify the default $prefix and
$exec_prefix (by default both is /usr).
Everything what you need is to check for non-default $exec_prefix in
configure script, in such case you have to follow the prefix at all.
configure.ac:
AC_PREFIX_DEFAULT([/usr])
# Check whether exec_prefix=/usr:
case $exec_prefix:$prefix in
NONE:NONE | NONE:/usr | /usr:*)
AC_MSG_NOTICE([Default --exec-prefix detected.])
case $bindir in
'${exec_prefix}/bin') bindir=/bin
AC_MSG_NOTICE([ --bindir defaults to /bin]) ;;
esac
case $sbindir in
'${exec_prefix}/sbin') sbindir=/sbin
AC_MSG_NOTICE([ --sbindir defaults to /sbin]) ;;
esac ;;
esac
config/include-Makefile.am (included in all Makefiles):
# The original default values of bindir and sbindir:
usrbinexecdir = ${exec_prefix}/bin
usrsbinexecdir = ${exec_prefix}/sbin
Karel
--
Karel Zak <kzak@redhat.com>
prev parent reply other threads:[~2009-01-15 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 19:49 Add rulesdir to libudev.pc Marcel Holtmann
2009-01-08 21:43 ` Kay Sievers
2009-01-08 22:47 ` Marcel Holtmann
2009-01-08 22:54 ` Kay Sievers
2009-01-15 22:59 ` Karel Zak [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090115225951.GC7646@nb.net.home \
--to=kzak@redhat.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).