All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] hidapi: new package
Date: Tue, 17 Nov 2015 10:11:26 +0000	[thread overview]
Message-ID: <564AFD4E.2000301@imgtec.com> (raw)
In-Reply-To: <20151116180724.GK9908@tarshish>

Hello Baruch,

On 11/16/2015 06:07 PM, Baruch Siach wrote:
> Hi Vincent,
> 
> On Mon, Nov 16, 2015 at 04:54:12PM +0000, Vicente Olivert Riera wrote:
>> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> 
> [...]
> 
>> +HIDAPI_DEPENDENCIES = libusb
>> +# When eudev is used as the udev provider, libgudev is automatically
>> +# provided as it is part of eudev. However, when systemd is used as the
>> +# udev provider, libgudev is not provided, and needs to be built
>> +# separately. This is why we select the libgudev package only if systemd
>> +# is used.
>> +ifeq ($(BR2_PACKAGE_SYSTEMD),y)
> 
> Should be 'ifeq ($(BR2_PACKAGE_LIBGUDEV),y)', in think, since all we need is 
> to have libgudev built before this package, regardless of systemd. With this 
> change the comment becomes redundant. The comment in Config.in should be 
> enough.

we need libgudev only if we are going to use systemd. Otherwise it will
be provided by eudev.

Of course we could use ifeq ($(BR2_PACKAGE_LIBGUDEV),y) here, but, for
consistency with Config.in, I use ifeq ($(BR2_PACKAGE_SYSTEMD),y)
instead. See for instance the udisks package.

Regards,

Vincent.

>> +HIDAPI_DEPENDENCIES += libgudev
>> +endif
> 
> baruch
> 

  reply	other threads:[~2015-11-17 10:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 16:54 [Buildroot] [PATCH] hidapi: new package Vicente Olivert Riera
2015-11-16 18:07 ` Baruch Siach
2015-11-17 10:11   ` Vicente Olivert Riera [this message]
2015-11-18  4:50     ` Baruch Siach
2015-11-18  8:22       ` Thomas Petazzoni
2015-11-18  8:45         ` Baruch Siach
2015-11-18  8:55           ` Thomas Petazzoni
2015-11-17 21:04 ` Thomas Petazzoni
2015-11-26  4:14 ` Alan Ott

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=564AFD4E.2000301@imgtec.com \
    --to=vincent.riera@imgtec.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.