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 1/1] ola: new package
Date: Wed, 14 Aug 2013 00:32:11 +0200	[thread overview]
Message-ID: <20130814003211.0c9bdaa7@skate> (raw)
In-Reply-To: <1376330715-20047-1-git-send-email-blanco.ether@gmail.com>

Dear Dave Skok,

On Mon, 12 Aug 2013 14:05:15 -0400, Dave Skok wrote:
> Signed-off-by: Dave Skok <blanco.ether@gmail.com>
> ---
>  package/Config.in     |   1 +
>  package/ola/Config.in | 144 +++++++++++++++++++++++++++++++++++++++++++++++
>  package/ola/ola.mk    | 153 ++++++++++++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 298 insertions(+)
>  create mode 100644 package/ola/Config.in
>  create mode 100644 package/ola/ola.mk

Thanks, it now builds successfully.

However, I've found another issue: even if I keep most plugins
disabled, they are still all built and installed. For example, with a
configuration that has:

# BR2_PACKAGE_OLA_PLUGIN_KARATE is not set

I get the karate plugin built and installed:

$ ls -1 output/target/usr/lib/olad/*karate*
output/target/usr/lib/olad/libolakarate.so
output/target/usr/lib/olad/libolakarate.so.0
output/target/usr/lib/olad/libolakarate.so.0.0.0

Same goes for:

# BR2_PACKAGE_OLA_PLUGIN_SPI is not set

$ ls -1 output/target/usr/lib/olad/*spi*
output/target/usr/lib/olad/libolaspicore.so
output/target/usr/lib/olad/libolaspicore.so.0
output/target/usr/lib/olad/libolaspicore.so.0.0.0
output/target/usr/lib/olad/libolaspi.so
output/target/usr/lib/olad/libolaspi.so.0
output/target/usr/lib/olad/libolaspi.so.0.0.0

Is this expected?

Thanks,

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

  reply	other threads:[~2013-08-13 22:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 18:05 [Buildroot] [PATCH 1/1] ola: new package Dave Skok
2013-08-13 22:32 ` Thomas Petazzoni [this message]
2013-08-14  0:51   ` Blanco
     [not found]     ` <CALy4uEU8nED=gPosezp_5dK79BQ8Q18ZtogJhPComrO+kHkJZA@mail.gmail.com>
2013-08-15 14:30       ` [Buildroot] Fwd: " David Skok
2013-08-15 15:11         ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2013-08-28 11:50 [Buildroot] " Dave Skok
2013-09-12 21:03 ` Peter Korsgaard
2013-08-26 14:02 Dave Skok
2013-08-27  8:04 ` Thomas De Schampheleire
2013-08-27 16:57 ` Arnout Vandecappelle
2013-08-28 11:51   ` David Skok
2013-08-15 17:04 Dave Skok
2013-08-22  8:25 ` Thomas De Schampheleire
2013-08-26 12:36   ` David Skok
2013-08-07 13:10 Dave Skok
2013-08-10 17:13 ` Thomas Petazzoni
     [not found]   ` <CALy4uEXhixrLNKzrRVsdYqCeNer6XPB_kXKwJepH8Pnh9+M+mA@mail.gmail.com>
2013-08-12 18:01     ` Thomas Petazzoni
2013-08-12 18:36       ` David Skok

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=20130814003211.0c9bdaa7@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