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 v2 1/2] pcsc-lite: new package
Date: Thu, 20 Sep 2012 12:22:57 +0200	[thread overview]
Message-ID: <20120920122257.359e35d6@skate> (raw)
In-Reply-To: <99B09243E1A5DA4898CDD8B70011144818039905B8@EXMB04.eu.tieto.com>

Dear Waldemar Rymarkiewicz,

On Thu, 20 Sep 2012 09:10:26 +0300, Waldemar.Rymarkiewicz at tieto.com
wrote:

> >Why when udev is available you don't do need libusb? Also, if udev is
> >available, you need to add it to the list of dependencies.
> 
> This is how pcsc-lite  ./configure  works. 
> 
> Firstly, libudev and libusb can't be used together. That means if you --enable-libusb you have to --disable-libudev (by default is enabled) explicitly.
> 
> Secondly,  ./configure gives priority to libudev to be used if found, otherwise it searches for libusb.
> 
> Finally, Neither libusb nor libudev can be found then no usb devices are used (serial only). Then --disable-libudev --disable-libusb will still compile. 
> 
> The only concern I have now it that user has to know this dependencies and select libusb or libudev explicitly. So wandering if not to require libusb or libudev in this package. What's your opinion?

Samuel and Arnout have replied on the ways to make it possible.

On my side, I'm still surprised that either udev or libusb are needed.
They do really two different things, and I don't see how having udev
can replace what libusb is doing, except if libusb is only used for USB
device enumeration, and not access to the USB devices themselves. But I
haven't looked at the code.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2012-09-20 10:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 12:52 [Buildroot] [PATCH v2 1/2] pcsc-lite: new package Waldemar Rymarkiewicz
2012-09-19 12:52 ` [Buildroot] [PATCH v2 2/2] ccid: " Waldemar Rymarkiewicz
2012-09-19 20:56   ` Arnout Vandecappelle
2012-09-20  6:31     ` Waldemar.Rymarkiewicz at tieto.com
2012-09-19 14:47 ` [Buildroot] [PATCH v2 1/2] pcsc-lite: " Thomas Petazzoni
2012-09-20  6:10   ` Waldemar.Rymarkiewicz at tieto.com
2012-09-20  7:36     ` Samuel Martin
2012-09-20  8:01       ` Waldemar.Rymarkiewicz at tieto.com
2012-09-20  9:27     ` Arnout Vandecappelle
2012-09-20 10:22     ` Thomas Petazzoni [this message]
2012-09-19 20:41 ` Arnout Vandecappelle
2012-09-20  6:12   ` Waldemar.Rymarkiewicz at tieto.com

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=20120920122257.359e35d6@skate \
    --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