All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] swupdate: improved help text for Lua support
Date: Fri, 29 Jul 2016 18:14:36 +0200	[thread overview]
Message-ID: <1469808876.3805.4.camel@embedded.rocks> (raw)
In-Reply-To: <5f0bb3f1-3f91-0bf0-8677-790dad5e92fe@yelloz.me>

On Mo, 2016-07-25 at 09:36 -0700, Jordan Yelloz wrote:

On 07/25/2016 12:32 AM, Thomas Petazzoni wrote:


Hello,

On Sun, 24 Jul 2016 16:27:38 -0700, Jordan Yelloz wrote:



-	??* Select BR2_PACKAGE_LUA if you want to have Lua
support.
+	??* Select BR2_PACKAGE_LUA or BR2_PACKAGE_LUAJIT if you
want to have Lua
+	????support.
+	????CONFIG_HANDLER_IN_LUA is not supported in LuaJIT or
Lua 5.1.
+	????swupdate must be manually configured with
CONFIG_LUAVERSION="jit-5.1"
+	????to link against luajit.


What does this last sentence means?

Thomas



Regarding CONFIG_LUAVERSION, this is trying to explain how to
successfully configure swupdate to build against LuaJIT. If you just
choose LuaJIT, it will not be successful automatically due to some
minor
limitations in the swupdate build system.

swupdate has some build rules that are not that good (it uses
pkg-config for some parts of the build but uses a secondary list of
library names to actually link the final executable against) and when
adding the Lua library to the list of libraries to link, it relies on
concatenating "lua" with $(CONFIG_LUAVERSION).

Basically, the only way to get swupdate to link against libluajit-
5.1.so
is to ensure CONFIG_LUAVERSION="jit-5.1" is in your swupdate KConfig
file. To me, the easiest/safest way of handling that is to expect the
user to configure swupdate manually with that value.


I like the idea of using swupdate with LuaJIT!

How about setting LUAVERSION if LuaJIT is selected? Like adding this somewhere:

$(call KCONFIG_SET_OPT,CONFIG_LUAVERSION,"jit-5.1")

Best regards
J?rg Krause

  reply	other threads:[~2016-07-29 16:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-24 23:27 [Buildroot] [PATCH 0/4] swupdate: allow configuring with LuaJIT Jordan Yelloz
2016-07-24 23:27 ` [Buildroot] [PATCH 1/4] swupdate: allowed luajit to enable HAVE_LUA Jordan Yelloz
2016-07-25  7:31   ` Thomas Petazzoni
2016-07-25 16:46     ` Jordan Yelloz
2016-10-25 11:56   ` Thomas Petazzoni
2016-07-24 23:27 ` [Buildroot] [PATCH 2/4] swupdate: updated lua check for libconfig Jordan Yelloz
2016-07-29 16:15   ` Jörg Krause
2016-10-25 19:36   ` Thomas Petazzoni
2016-07-24 23:27 ` [Buildroot] [PATCH 3/4] swupdate: improved help text for Lua support Jordan Yelloz
2016-07-25  7:32   ` Thomas Petazzoni
2016-07-25 16:36     ` Jordan Yelloz
2016-07-29 16:14       ` Jörg Krause [this message]
2016-07-29 20:28         ` Jordan Yelloz
2016-10-25 19:43   ` Thomas Petazzoni
2016-07-24 23:27 ` [Buildroot] [PATCH 4/4] swupdate: added a warning for LuaJIT/Lua 5.1 Jordan Yelloz
2016-07-29 16:20   ` Jörg Krause
2016-07-29 16:32     ` Jordan Yelloz
2016-07-29 16:38       ` Jörg Krause
2016-10-25 19:43     ` Thomas Petazzoni

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=1469808876.3805.4.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.