Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] pcsc-lite: new package
Date: Sun, 30 Sep 2012 16:59:48 +0200	[thread overview]
Message-ID: <50685E64.8040908@mind.be> (raw)
In-Reply-To: <1348212739-32093-1-git-send-email-waldemar.rymarkiewicz@tieto.com>

On 21/09/12 09:32, Waldemar Rymarkiewicz wrote:
> Middleware to access a smart card using SCard API (PC/SC).
>
> http://pcsclite.alioth.debian.org/
>
> Signed-off-by: Waldemar Rymarkiewicz<waldemar.rymarkiewicz@tieto.com>
[snip]
> +config BR2_PACKAGE_PCSC_LITE_FORCE_LIBUSB
> +	bool "use libusb"
> +	depends on !BR2_PACKAGE_UDEV
> +	select BR2_PACKAGE_LIBUSB

  This one is missing a help text.

[snip]
> +# - libudev and libusb are optional
> +# - libudev and libusb can't be used together
> +# - libudev has a priority over libusb

  Well put!

> +
> +ifeq ($(BR2_PACKAGE_UDEV),y)
> +PCSC_LITE_CONF_OPT += --enable-libudev --disable-libusb
> +PCSC_LITE_DEPENDENCIES += udev
> +else
> +ifeq ($(BR2_PACKAGE_LIBUSB),y)
> +PCSC_LITE_CONF_OPT += --enable-libusb --disable-libudev
> +PCSC_LITE_DEPENDENCIES += libusb
> +else
> +PCSC_LITE_CONF_OPT += --disable-libusb --disable-libudev
> +endif
> +endif
> +
> +ifeq ($(PACKAGE_PCSC_LITE_DEBUGATR),y)
> +PCSC_LITE_CONF_OPT += --enable-debugatr
> +endif
> +
> +ifeq ($(PACKAGE_PCSC_LITE_EMBEDDED),y)
> +PCSC_LITE_CONF_OPT += --enable-embedded
> +endif

  There is also a --enable-usbdropdir which defaults to
/usr/local/lib/pcsc/drivers.  We avoid using /usr/local, so could
you make that point to /usr/lib/pcsc/drivers?  Or is it anyway
not used?


  Regards,
  Arnout

> +
> +$(eval $(call autotools-package))

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2012-09-30 14:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21  7:32 [Buildroot] [PATCH v3 1/2] pcsc-lite: new package Waldemar Rymarkiewicz
2012-09-21  7:32 ` [Buildroot] [PATCH v3 2/2] ccid: " Waldemar Rymarkiewicz
2012-09-24 11:56   ` Waldemar.Rymarkiewicz at tieto.com
2012-09-26  8:00   ` Waldemar.Rymarkiewicz at tieto.com
2012-09-26  8:03     ` Peter Korsgaard
2012-09-26  8:06       ` Waldemar.Rymarkiewicz at tieto.com
2012-09-30 15:11   ` Arnout Vandecappelle
2012-10-05  9:57     ` Waldemar.Rymarkiewicz at tieto.com
2012-09-30 14:59 ` Arnout Vandecappelle [this message]
2012-10-01  5:44   ` [Buildroot] [PATCH v3 1/2] pcsc-lite: " Waldemar.Rymarkiewicz at tieto.com
2012-10-02 16:08     ` Arnout Vandecappelle

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=50685E64.8040908@mind.be \
    --to=arnout@mind.be \
    --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