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 04/12] lbase64: New package
Date: Wed, 22 May 2013 09:01:37 +0200	[thread overview]
Message-ID: <20130522090137.721cbaac@skate> (raw)
In-Reply-To: <519C636D.9010805@mind.be>

Dear Arnout Vandecappelle,

On Wed, 22 May 2013 08:19:25 +0200, Arnout Vandecappelle wrote:
> On 20/05/13 19:25, Thomas Petazzoni wrote:
> >> >Also, regarding the static library, the output of the package is always a
> >> >shared object since it needs to be loaded dynamically by Lua scripts. The
> >> >default target of the package is a test so I need to specifically specify
> >> >the target.
> > Ok. Then maybe your package needs to depend on !BR2_PREFER_STATIC_LIB.
> > Or maybe more of the Lua stuff, if it requires shared libraries.
> 
>   We currently probably have many packages that generate .so files even 
> if PREFER_STATIC_LIB is true

Correct, but...

> - that's why it is "prefer", right?
> 
>   That said, I'm certainly in favour of making the STATIC stuff more strict.

... I dislike this idea of "prefer". I would like the
BR2_PREFER_STATIC_LIB option be turned into something like "Fully
static system", because this is also what is needed for non-MMU
platforms that have no shared library support. I don't really see the
point of having something that will "prefer static libraries" for some
packages and not for some other, without control on which ones. Of
course, if we could control on a per-package basis which library should
be built static and which should be built shared, this would make some
sense. But without such control, it really doesn't make any sense to me
to have a random selection of packages being built shared, and the rest
being built static, when you enable BR2_PREFER_STATIC_LIB=y.

So, to me, while this option is still named BR2_PREFER_STATIC_LIB, we
should think of it as BR2_USE_ONLY_STATIC_LIB. Maybe someday we'll
rename it? :-)

Of course, that raises the question of whether we should disable all
libraries/applications that use dlopen() libraries when this option is
enabled.

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:[~2013-05-22  7:01 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 12:56 [Buildroot] [PATCH 01/12] coxpcall: Updated source location Assaf Inbal
2013-05-20 12:56 ` [Buildroot] [PATCH 02/12] luasocket: Update " Assaf Inbal
2013-06-16 19:47   ` Peter Korsgaard
2013-06-17  5:18     ` Assaf Inbal
2013-05-20 12:56 ` [Buildroot] [PATCH 03/12] sqlite: Added host compilation support Assaf Inbal
2013-05-20 13:26   ` Yann E. MORIN
2013-05-20 14:27     ` Assaf Inbal
2013-05-20 16:00       ` Yann E. MORIN
2013-05-20 12:56 ` [Buildroot] [PATCH 04/12] lbase64: New package Assaf Inbal
2013-05-20 14:52   ` Thomas Petazzoni
2013-05-20 15:23     ` Assaf Inbal
2013-05-20 17:25       ` Thomas Petazzoni
2013-05-22  6:19         ` Arnout Vandecappelle
2013-05-22  6:55           ` Assaf Inbal
2013-05-22  7:28             ` Thomas Petazzoni
2013-05-22  7:01           ` Thomas Petazzoni [this message]
2013-05-22  7:06             ` Arnout Vandecappelle
2013-05-22  7:29               ` Bryan Hundven
2013-05-22  7:42                 ` Thomas Petazzoni
2013-05-22  7:46                   ` Bryan Hundven
2013-05-22  7:30               ` Thomas Petazzoni
2013-05-20 16:00   ` François Perrad
2013-06-16 19:52     ` Peter Korsgaard
2013-06-17  5:31       ` Assaf Inbal
2013-06-17 20:59         ` Peter Korsgaard
2013-05-20 12:56 ` [Buildroot] [PATCH 05/12] lua-ev: " Assaf Inbal
2013-05-20 16:05   ` François Perrad
2013-06-16 19:53     ` Peter Korsgaard
2013-06-17  5:58       ` Assaf Inbal
2013-06-17 21:14         ` Peter Korsgaard
2013-05-20 12:56 ` [Buildroot] [PATCH 06/12] luabitop: " Assaf Inbal
2013-06-16 20:03   ` Peter Korsgaard
2013-05-20 12:56 ` [Buildroot] [PATCH 07/12] luacrypto: " Assaf Inbal
2013-05-20 16:07   ` François Perrad
2013-06-16 20:16     ` Peter Korsgaard
2013-06-17  6:18       ` Assaf Inbal
2013-06-17 21:18         ` Peter Korsgaard
2013-05-20 12:56 ` [Buildroot] [PATCH 08/12] luaexpatutils: " Assaf Inbal
2013-06-19 21:24   ` Peter Korsgaard
2013-05-20 12:56 ` [Buildroot] [PATCH 09/12] luaposix: " Assaf Inbal
2013-05-20 16:09   ` François Perrad
2013-06-19 21:34   ` Peter Korsgaard
2013-06-20  4:45     ` Assaf Inbal
2013-06-20  5:57       ` Arnout Vandecappelle
2013-06-20  6:10       ` Thomas Petazzoni
2013-06-20  7:05         ` Assaf Inbal
2013-06-20  7:39           ` Assaf Inbal
2013-06-20  7:46             ` Thomas Petazzoni
2013-05-20 12:56 ` [Buildroot] [PATCH 10/12] luasec: " Assaf Inbal
2013-05-20 16:10   ` François Perrad
2013-08-12 17:46   ` Thomas Petazzoni
2013-05-20 12:56 ` [Buildroot] [PATCH 11/12] luasql: " Assaf Inbal
2013-05-20 16:13   ` François Perrad
2013-08-12 17:47   ` Thomas Petazzoni
2013-05-20 12:56 ` [Buildroot] [PATCH 12/12] orbit: " Assaf Inbal
2013-08-13  9:53   ` Thomas Petazzoni
2013-08-13 10:16     ` Assaf Inbal
2013-06-16 19:46 ` [Buildroot] [PATCH 01/12] coxpcall: Updated source location Peter Korsgaard
2013-06-17  5:17   ` Assaf Inbal

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=20130522090137.721cbaac@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