From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5] luvi: new package
Date: Sat, 26 Dec 2015 10:52:44 +0100 [thread overview]
Message-ID: <20151226105244.14556b27@free-electrons.com> (raw)
In-Reply-To: <1451080268.16818.8.camel@embedded.rocks>
J?rg,
On Fri, 25 Dec 2015 22:51:08 +0100, J?rg Krause wrote:
> > Thanks, patch applied. I must say I don't really understand what this
> > luvi thing is doing, but it built fine here, and the packaging seems
> > reasonable.
>
> luvi is a LuaJIT runtime with additional bindings, e.g. libuv. You can
> compare it with the V8 engine (the JavaScript engine used by Node.js),
> the main difference is, that luvi already contains the libuv bindings,
> whereas Node.js adds the libuv bindings to V8.
>
> All together, it is a Node.js like system for Lua.
Thanks a lot for the explanation, makes sense!
> I want to integrate some luvi applications like lit and luvit into
> Buildroot. lit is similar to npm and luvit adds a Node.js like API to
> luvi.
>
> This will be done in follow-up patches...
Cool!
> > as this ?.lua doesn't really look like a path, but since it builds
> > fine, maybe I'm missing something.
>
> Lua(JIT) uses this string as a path to search for files. In this case
> we have to tell LuaJIT where to search for its bundled modules.
Ok. So this "?" is interpreted by LuaJIT in a "special" way.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-12-26 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 7:45 [Buildroot] [PATCH v5] luvi: new package Jörg Krause
2015-12-20 22:28 ` Thomas Petazzoni
2015-12-25 21:51 ` Jörg Krause
2015-12-26 9:52 ` 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=20151226105244.14556b27@free-electrons.com \
--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