From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Discussing libudev, was: Re: [PATCH v6 09/32] mesa3d: dri2 does not need udev support
Date: Mon, 12 May 2014 23:50:40 +0200 [thread overview]
Message-ID: <20140512235040.1be8bbb0@free-electrons.com> (raw)
In-Reply-To: <g2q74bxv7r.ln2@ID-313208.user.individual.net>
Dear Bernd Kuhls,
On Mon, 12 May 2014 23:12:16 +0200, Bernd Kuhls wrote:
> I copied the systemd package and build only the libudev part, short snippets
> from my hacky package:
>
> LIBUDEV_VERSION = 212
> LIBUDEV_SITE = http://www.freedesktop.org/software/systemd/
> LIBUDEV_SOURCE = systemd-$(LIBUDEV_VERSION).tar.xz
> [...]
> define LIBUDEV_BUILD_CMDS
> $(TARGET_MAKE_ENV) $(MAKE1) -C $(@D) \
> src/libudev/libudev.pc \
> src/shared/errno-from-name.h \
> src/shared/errno-to-name.h \
> src/shared/af-from-name.h \
> src/shared/af-to-name.h
> $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) libudev.la
> endef
>
> followed by some LIBUDEV_INSTALL_STAGING/TARGET_CMDS file copying.
To be honest, this seems quite hacky to me, and fragile for future
version bumps.
If you run a complete monster software such as XBMC, I'm pretty sure
your platform can also afford to run either eudev or systemd, no?
In Buildroot, we've always tried to avoid going *against* upstream
decisions. The decision of upstream for udev is to bundle it as part of
systemd. Gentoo has decided to provide a maintained fork of udev as
eudev, so we support both options. But I definitely wouldn't want to
support things that are completely Buildroot-specific.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-05-12 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 19:55 [Buildroot] Discussing libudev, was: Re: [PATCH v6 09/32] mesa3d: dri2 does not need udev support Bernd Kuhls
2014-05-12 20:53 ` Yann E. MORIN
2014-05-12 20:59 ` Bernd Kuhls
2014-05-12 21:02 ` Thomas Petazzoni
2014-05-12 21:12 ` Bernd Kuhls
2014-05-12 21:50 ` Thomas Petazzoni [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=20140512235040.1be8bbb0@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.