From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/qt5base: add optional dependency on udev
Date: Fri, 24 Jun 2016 18:05:34 +0200 [thread overview]
Message-ID: <20160624180534.7535ffd9@free-electrons.com> (raw)
In-Reply-To: <1466665515-26237-1-git-send-email-yann.morin@orange.com>
Hello,
On Thu, 23 Jun 2016 09:05:15 +0200, Yann E. MORIN wrote:
> Qt5 can optionally enable udev support, especially to enumerate input
> devices dynamically. Without udev, devices are not properly enumerated,
> and any device that is not present at launch time is never seen (there
> is no support for hotplug, that is).
>
> Currently, Qt5base has no explicit dependency on udev, so it will all
> depend on the build order. Sometimes, a package that requires udev will
> be built before qt5base and Qt5 will have support for udev, sometime no
> such package is built before qt5base and Qt5 will not have support for
> udev.
>
> Add an explicit dependency on udev, but only if it is enabled.
>
> Note: this only really requires libudev, but we do not yet have a
> separate libudev; we still only have a udev provider (be it eudev or
> systemd).
>
> Signed-off-by: "Yann E. MORIN" <yann.morin@orange.com>
> Cc: Cedric Chedaleux <cedric.chedaleux@orange.com>
> ---
> package/qt5/qt5base/qt5base.mk | 5 +++++
> 1 file changed, 5 insertions(+)
As suggested by Arnout, I've dropped the comment that isn't very
useful, and applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-06-24 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 7:05 [Buildroot] [PATCH] package/qt5base: add optional dependency on udev Yann E. MORIN
2016-06-23 21:00 ` Arnout Vandecappelle
2016-06-24 16:05 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-22 12:44 Yann E. MORIN
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=20160624180534.7535ffd9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox