On 19 June 2011 16:59, Oisín <[email protected]> wrote:
> The batch file makes hardcoded assumptions about the name of the
> interpreter and the lua DLL - I can't remember how I got past this using
> LuaJIT the first time (probably renaming/copying them, lazy as usual), so
> this time I just tweaked the installer to accept an /INT parameter with the
> interpreter name, and just added a check for lua51.dll somewhere.
>
> Then I tried to install Luasocket again and was reminded that it will not
> work. Must read up on this 'builtin' type and see what can be done...
>
> Tiny diff of installer.bat attached.
Hi guys,
Am I the only one using Luajit + LR + Windows, or is there a better way of
making this work? There were no comments on this, but Luarocks still
doesn't work out of the box with Luajit as the default interpreter, so
maybe I'm the only one struggling with it.
There seems to be a "--lua-suffix" option in the *nix configure script, but
none with the Windows installer, hence this modification.
I wouldn't mind if LR used its own copy of Lua, except that packages with
compiled code then cause Luajit to crash if they're not compiled against
its Lua library.
Oisín
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Luarocks-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
