Closed GoogleCodeExporter closed 9 years ago
I am not sure. I don't have an easy way to use Windows 7 to check this.
@Steve,
Can you test this out in your Windows 7 install?
Original comment by rpusz...@gmail.com
on 7 May 2010 at 1:38
Hey,
whenever I start lua and type
require "luanet"
it crashes. I have tested this on XP and Vista machines. I would appreciate if
you
could find the reason.
Original comment by Benjamin...@gmail.com
on 13 May 2010 at 11:30
I've put up a patch for LuaInterface which has been tested on Windows 7; should
work
on Vista.
Requires .NET 2.0
Download LuaInterface-patch-20.zip from the Downloads page, and unzip into the
Lua
install directory (usually C:\Program Files). It puts new versions of
luanet.dll and
LuaInterface.dll into the clibs folder.
steve d.
Original comment by steve.j....@gmail.com
on 14 May 2010 at 6:11
Hey Steve,
thanks for the patch - works well!
Ben
Original comment by Benjamin...@gmail.com
on 14 May 2010 at 3:27
Glad that helped, Ben! One issue that I found was that the env var LUA_CPATH
was not
defined for a regular Win 7 install! LUA_DEV was, so I just used that ;) But
there's
definitely an install issue on Vista/7 underlying it.
Original comment by steve.j....@gmail.com
on 14 May 2010 at 4:32
Thank you!
Original comment by lexazloy
on 15 May 2010 at 7:51
Updated for the next release of LfW
Original comment by rpusz...@gmail.com
on 18 May 2010 at 6:45
Hi all,
I'm very new to lua and very interested in the luainterface work. I've
downloaded the
lfw 5.1.4-37 and I get the same situation described in comment 2 after applying
the
LuaInterface-patch-20.zip.
My OS is xp. I have .net framework 2.0 sp2 installed. I checked my env variable
I
have the following:
LUA_PATH=;;C:\Program Files\Lua\5.1\lua\?.luac
LUA_DEV=C:\Program Files\Lua\5.1
Any help appreciated! Thanks
Chris
Original comment by chris.ch...@gmail.com
on 25 May 2010 at 8:42
I figured out that I will need to restart command prompt after I fiddle with
the env
variable. Sorry for the school boy mistake. The patch works well thanks alot!
Chris
Original comment by chris.ch...@gmail.com
on 25 May 2010 at 8:47
Hi Chris,
We have _all_ learned the hard way that environment variable don't get set in
the
current command prompt!
But what interests me is why you needed to change the environment variables.
The new
LuaInterface version only relies on LUA_DEV, which should be set up nicely by
your
LfW install
steve d.
Original comment by steve.j....@gmail.com
on 25 May 2010 at 9:03
Hi all,
I'm new to Lua... and this is my (brief) story:
1) Installed Lua on a Windows 7 machine
1a) Called a simple Lua script from a C# program: OK. (The script didn't
contain "require 'luanet'"
1b) Wrote the command "require 'luanet'" in a Lua shell: KO (Lua crashed)
2) Installed the patch LuaInterface-patch-20.zip
2a) Command "require 'luanet'" in Lua shell: OK
2b) Called a simple Lua script from a C# program: KO. Compilation gone well,
but when I tried to run the programm, I got an exception on the followin line:
private Lua luaEngine = new Lua();
The exception is:
"An unhandled exception of type 'System.DllNotFoundException' occurred in
LuaInterface.dll
Additional information: Unable to load DLL 'luanet.dll': The specified module
could not be found. (Exception from HRESULT: 0x8007007E)"
I tried put a copy of luanet.dll in various directory but that didn't help.
Any suggestion?
Any help appreciated! Thanks
Giulio
Original comment by GiulioDe...@gmail.com
on 16 Jun 2010 at 4:28
I observe the same exception being thrown as mentioned in comment 11.
I am using Windows 7, 32 bit, Visual Studio 2010, .net Framework 4.0.xxx and
LUA 5.1.4-40 without the patch since it says that it refers only to versions
before and including 5.1.3-38.
For me it does not even work if LUA_PATH and LUA_CPATH contain "." and
luanet.dll lies in the current directory next to the *.exe.
Original comment by ge...@bisseling.de
on 6 Oct 2010 at 10:14
So as it stands Lua is crap, 2 years later and it still has the same problems.
Seems Windows 7 is not one of the target markets. I think I will stick with
Python.Net, at least it works.
Original comment by andrew.v...@gmail.com
on 25 Jun 2012 at 9:11
Yes, Lua for Windows is getting old. But the action is shifting
towards using the Batteries package of LuaDist:
http://lua-users.org/lists/lua-l/2012-04/msg00908.html
This will become the new Lua for Windows, with the bonus of being
cross-platform, and moving away from the old crappy VS2005 runtime.
As for LuaInterface, I've been working on a more portable version
based on the 2.0.3 release, which will find its way into LuaDist.
steve d.
Original comment by steve.j....@gmail.com
on 26 Jun 2012 at 6:13
Original issue reported on code.google.com by
lexazloy
on 7 May 2010 at 7:47