lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Hello Hisham


I might as well ask this question again, just on the off chance its been fixed (or at least the problem understood ?).


I have tried several times and wasted lots of hours trying to get LuaRocks to work in the past with no joy, I always got a failure at Link time when building even a simple library. This was due to the fact that I am a LuaForWindows user. Presumably there is an incompatibility there between the Lua Binaries in LuaForWindows package and LuaRocks ?


The advice to fix it was always delete existing Lua51 Binaries and rebuild lua from scratch. I wasnt prepared to do that I had lots of projects working fine with the LuaForWindows package, I didnt want to risk breaking my working projects which would be very likely I think if I got the LuaRocks library linking OK.


For info I was running on Windows 7, Lua 5.1 and trying to build a LuaRocks library using MS Visual Studio 2013.


Thanks for any update info regarding using LuaRocks after a LuaForWindows install.

From: lua-l-bounces@lists.lua.org <lua-l-bounces@lists.lua.org> on behalf of Hisham <h@hisham.hm>
Sent: 06 October 2016 20:11:19
To: Lua mailing list
Subject: [ANN] LuaRocks 2.4.1
 
Hello, list!

This is a minor bugfix release of LuaRocks 2.4.1. LuaRocks is a
package management system for Lua modules. (For more information,
please visit http://luarocks.org )

http://luarocks.org/releases/luarocks-2.4.1.tar.gz
http://luarocks.org/releases/luarocks-2.4.1-win32.zip

Those of you on Unix who are running LuaRocks as a rock (i.e. those
who previously installed using `make bootstrap`) can install it using:

   luarocks install luarocks

What's new since 2.4.0:

* Avoid coroutine use inside luarocks.loader, that apparently affected
OpenResty's require()
* Fix upgrade issues for old versions (e.g. when upgrading from LuaRocks 2.1.0)

Special thanks for Michal Cichra and Tomás Guisasola for reporting
these bugs. This release contains commits by Peter Melnichenko and
myself.

As always, all kinds of feedback is greatly appreciated.

Thank you, enjoy!

-- Hisham