From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lua: remove shared library feature
Date: Thu, 15 Aug 2013 19:07:02 +0200 [thread overview]
Message-ID: <20130815190702.3df811a5@skate> (raw)
In-Reply-To: <CAB0FRss5gTuePkganj6UfXg0ssqQADc_rAya90znq-=6zVfDwg@mail.gmail.com>
Dear Fran?ois Perrad,
On Thu, 15 Aug 2013 18:56:48 +0200, Fran?ois Perrad wrote:
> 2013/8/14 Thomas Petazzoni <thomas.petazzoni@free-electrons.com>:
> > Fran?ois, Gustavo,
> >
> > Can you look at the below patch and tell me what you think?
> >
>
> Seems obsolete (BR2_PACKAGE_LUA_SHARED_LIBRARY was removed).
The option was removed because we now always build a shared library.
But the idea of the patch we're discussing was to remove the
possibility of building a shared library for Lua since this isn't
supported upstream, and we try to avoid having "feature" patches in
Buildroot.
For the moment, we still have
package/lua/lua-02-shared-libs-for-lua.patch and
package/lua/lua-03-shared-libs-for-luac.patch to support building a
shared library for Lua.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-15 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 12:45 [Buildroot] [PATCH] lua: remove shared library feature Arnout Vandecappelle
2013-08-13 22:36 ` Thomas Petazzoni
2013-08-15 16:56 ` François Perrad
2013-08-15 17:07 ` Thomas Petazzoni [this message]
2013-08-15 21:51 ` François Perrad
-- strict thread matches above, loose matches on Subject: below --
2012-11-04 12:43 Arnout Vandecappelle
2012-11-04 14:24 ` François Perrad
2012-11-04 19:02 ` 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=20130815190702.3df811a5@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