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] Add pcs-lite package to buildroot.
Date: Thu, 23 Sep 2010 00:00:33 +0100	[thread overview]
Message-ID: <20100923000033.05e9e9e5@surf> (raw)
In-Reply-To: <AANLkTinyYg2p72sarSbRWfxXqZVg_WpvvfQMVdk8ryMw@mail.gmail.com>

Hi !

On Wed, 22 Sep 2010 09:53:50 +0200
Belisko Marek <marek.belisko@gmail.com> wrote:

> +source "package/pcs-lite/Config.in"
> +#source "package/pcsc-tools/Config.in"

Keep this commented line for the patch on pcsc-tools.

> +#############################################################
> +#
> +# pcs-lite
> +#
> +#############################################################
> +PCS_LITE_VERSION = 1.6.4
> +PCS_LITE_SOURCE = pcs-lite-$(PCS_LITE_VERSION).tar.bz2
> +PCS_LITE_SITE = https://alioth.debian.org/frs/download.php/3337
> +PCS_LITE_AUTORECONF = NO

Not needed (that's the default).

> +PCS_LITE_INSTALL_STAGING = NO

Not needed (that's the default).

> +PCS_LITE_INSTALL_TARGET = YES

Not needed (that's the default).

> +PCS_LITE_CONF_OPT = --disable-libhal
> +
> +PCS_LITE_DEPENDENCIES = uclibc libusb

The dependency on 'uclibc' should be removed. Buildroot already knows
that the toolchain should be built prior to any user package.

If you depend on libusb, then your package should "select
BR2_PACKAGE_LIBUSB" in its Config.in file.

Regards,

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

      reply	other threads:[~2010-09-22 23:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22  7:53 [Buildroot] [PATCH] Add pcs-lite package to buildroot Belisko Marek
2010-09-22 23:00 ` Thomas Petazzoni [this message]

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=20100923000033.05e9e9e5@surf \
    --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