From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3 v2] package/eudev: introduce a host variant
Date: Fri, 01 Nov 2019 09:02:27 +0100 [thread overview]
Message-ID: <874kzohvn0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAJ4jsade6K=5V+kXMTaUhshbZ01t2k79SbxesCshdF85dwntFQ@mail.gmail.com> (Carlos Santos's message of "Tue, 29 Oct 2019 19:29:43 -0300")
>>>>> "Carlos" == Carlos Santos <unixmania@gmail.com> writes:
>> +++ b/package/eudev/eudev.mk
>> @@ -55,4 +55,40 @@ define EUDEV_USERS
>> - - kvm -1 * - - - kvm nodes
>> endef
>>
>> +HOST_EUDEV_DEPENDENCIES = host-gperf host-pkgconf
>> +
>> +HOST_EUDEV_SYSCONFDIR = $(if $(BR2_PACKAGE_SYSTEMD),/usr/lib,/etc)
>> +HOST_EUDEV_CONF_OPTS = \
>> + --prefix=/usr \
>> + --sbindir=/sbin \
>> + --libexecdir=/lib \
>> + --with-rootlibdir=/lib \
>> + --sysconfdir=$(HOST_EUDEV_SYSCONFDIR) \
> We don't actually need this, since /etc/udev/udevdb.bin is a valid
> location for systemd too. It was my idea, but I take it back. :-)
Are you sure that works? The sysconfdir is used both for the input and
output location. If you use systemd then the files provided by
systemd-udev presumably gets installed under /usr/lib/udev/hwdb.d as
well?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-11-01 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 22:07 [Buildroot] [PATCH 0/3 v2] udev providers: compile the hwdb at build time (branch yem/host-eudev-2) Yann E. MORIN
2019-10-29 22:07 ` [Buildroot] [PATCH 1/3 v2] package/eudev: introduce a host variant Yann E. MORIN
2019-10-29 22:29 ` Carlos Santos
2019-11-01 8:02 ` Peter Korsgaard [this message]
2019-11-01 8:02 ` Peter Korsgaard
2019-11-06 22:54 ` Peter Korsgaard
2019-10-29 22:07 ` [Buildroot] [PATCH 2/3 v2] package/eudev: generate the hwdb.bin Yann E. MORIN
2019-11-01 8:02 ` Peter Korsgaard
2019-11-06 22:54 ` Peter Korsgaard
2019-10-29 22:07 ` [Buildroot] [PATCH 3/3 v2] packagesystemd: " Yann E. MORIN
2019-11-01 8:03 ` Peter Korsgaard
2019-11-06 22:55 ` Peter Korsgaard
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=874kzohvn0.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.