Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tvheadend: add dependency on udev based rootfs creation
Date: Fri, 29 Dec 2017 14:40:31 +0100	[thread overview]
Message-ID: <20171229144031.798b5f81@windsurf.lan> (raw)
In-Reply-To: <20171229130604.9897-1-daggs@gmx.com>

Hello,

On Fri, 29 Dec 2017 15:06:04 +0200, Dagg Stompler wrote:
> BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV is needed for tvheadend inorder
> for the program to see usb based DVB cards.
> 
> Signed-off-by: Dagg Stompler <daggs@gmx.com>
> ---
>  package/tvheadend/Config.in | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/package/tvheadend/Config.in b/package/tvheadend/Config.in
> index 44a69a27ba..2a497b481d 100644
> --- a/package/tvheadend/Config.in
> +++ b/package/tvheadend/Config.in
> @@ -9,6 +9,7 @@ config BR2_PACKAGE_TVHEADEND
>  	depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL
>  	depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_2
>  	depends on BR2_TOOLCHAIN_HAS_SYNC_4
> +	depends on BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV

You should use BR2_PACKAGE_HAS_UDEV instead. Indeed udev can be
provided by either eudev or systemd.

This change will also require a change in the Config.in comment. See
package/dt-utils/Config.in for an example.

Also, does tvheadend needs to link with libudev ? If so, it should have
udev in its <pkg>_DEPENDENCIES. If it doesn't link with libudev, then
I'm not sure to see how udev helps for tvheadend to detect USB DVB
cards.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-12-29 13:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 13:06 [Buildroot] [PATCH] tvheadend: add dependency on udev based rootfs creation Dagg Stompler
2017-12-29 13:40 ` Thomas Petazzoni [this message]
2017-12-29 13:57   ` daggs
2017-12-29 14:03     ` Thomas Petazzoni
2017-12-29 14:27       ` daggs
2017-12-30  6:48         ` daggs
2017-12-29 13:55 ` Yann E. MORIN
2017-12-29 14:02   ` daggs

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=20171229144031.798b5f81@windsurf.lan \
    --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