Re: [ANN] Kepler 1.1

["Fabio Mascarenhas" <mascarenhas@...>]

Great to hear you've solved it. :-) Lua on Windows puts
%LOCATION_OF_EXE%\lua\?.lua in the LUA_PATH. LuaRocks exploits it by
putting lua5.1.exe in c:\LuaRocks\0.5.2, and the LuaRocks' modules in
c:\LuaRocks\0.5.2\lua. That's why you can load LuaRocks from the
console without setting LUA_PATH yourself. Executables that embed Lua,
such as xavante.exe, have to be put in the same path to use this
feature. That's why we advise thet you set /scripts to
C:\LuaRocks\0.5.2, everything then "just works".

--
Fabio Mascarenhas

On Wed, Jun 11, 2008 at 5:16 PM, Ignacio Burgueño
<ignaciob@inconcertcc.com> wrote:
> Fabio Mascarenhas wrote:
>>
>> Hi, Ignacio,
>>
>> Where is your xavante.exe? Put it in the same place as lua5.1.exe
>> (probably c:\LuaRocks\0.5.2) and it should work. I am trying to
>> convince Hisham to make the LuaRocks binaries' dir and "scripts" dir
>> the same, so other executables can work without setting LUA_PATH too.
>> I'll also put better OS detection on the next setup-kepler, thanks.
>> :-)
>
> He :) xavante.exe is in c:\LuaRocks\bin
> So that's what /SCRIPTS flag do...
> That pretty much covers all the issues, apart from the C runtimes clash, but
> I think I'll have to learn to live with that (is it LuaFileSystem related?)
>
>>
>> Oh, the scripts_dir == lr dir thing is documented in the installation
>> instructions for Windows
>> (http://www.keplerproject.org/en/Installation)
>
> Indeed, I was following the guide. But I had a previous install of LuaRocks
> and I overlooked the SCRIPTS flag.
>
> Regards,
> Ignacio
>