From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] ljsyscall: new package
Date: Thu, 30 Jan 2014 08:07:02 -0600 [thread overview]
Message-ID: <20140130080702.12041a96@core2quad.morethan.org> (raw)
In-Reply-To: <CANxTyt72FdGiCJ3zJO8JBB49DzLb4cE=YoiMiY-tBpn+T3azUA@mail.gmail.com>
On Thu, 30 Jan 2014 08:34:05 -0500
Danomi Manchego <danomimanchego123@gmail.com> wrote:
> Fran?ois,
>
> On Thu, Jan 30, 2014 at 6:46 AM, Fran?ois Perrad
> <francois.perrad@gadz.org> wrote:
> >> +LJSYSCALL_TARGET_DIR =
> >> $(TARGET_DIR)/usr/share/luajit-$(LUAJIT_VERSION)
> >
> > Danomi,
> >
> > I think that the right destination is :
> > LJSYSCALL_TARGET_DIR =
> > $(TARGET_DIR)/usr/share/lua/$(LUAINTERPRETER_ABIVER)
> >
> > 1) ljsyscall is designed for LuaJIT and PUC Lua + luaffi
>
> Looking through the README.md sections that mention Lua, it seems like
> the ability to work with non-LuaJIT is not a priority. E.g., "It now
> runs again with luaffi under standard Lua 5.2 (and probably 5.1,
> untested)." ("Runs again" makes it sound like it worked for while,
> lost compatibility, and maybe works again - does not inspire
> confidence.) Besides, buildroot does not [currently] have luaffi. So
> I don't think the Lua case is currently an option for a
> buildroot-generated system.
>
Ah, but it easily could.
I have used Lua Alien with 5.1 -
http://alien.luaforge.net/
Which requires libffi -
https://sourceware.org/libffi/
My particular use-case was to interface with binary blobs.
I have not built them with Buildroot, but outside of Buildroot.
So I do not have a BR patch handy to add them.
They required a bit of tweaking library pathnames to support
a multi-lib (desktop) layout but it should be possible to deal
with them inside of BR.
Mike
prev parent reply other threads:[~2014-01-30 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 3:10 [Buildroot] [PATCH v4 1/1] ljsyscall: new package Danomi Manchego
2014-01-20 21:43 ` Peter Korsgaard
2014-01-30 11:46 ` François Perrad
2014-01-30 13:34 ` Danomi Manchego
2014-01-30 14:07 ` Mike Zick [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=20140130080702.12041a96@core2quad.morethan.org \
--to=minimod@morethan.org \
--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