luaforwindows
luaforwindows copied to clipboard
The installer fails when trying to install vc redist
Run the installer from here: https://github.com/rjpcomputing/luaforwindows/releases/tag/v5.1.5-51 using "Run As Administrator".
Environment: Windows 10, processor: x64.
(if this is really a VS 2005 redist then it's quite old)
The installer failed but REPL seems to be working.
Yes it is built using visual studio 2005. That is the only option right now because Lua for Windows is only a binary distribution. It doesn't include modules it builds itself. And all of them were built with vs2005. There will be an effort soon to change to Lua 5.3 and LuaRocks. This way it becomes less modules but users can add more thru LuaRocks.
Hope this explanation helps.
Regards, Ryan
Sent from my phone
On Nov 5, 2016 4:32 AM, "Pawel Kadluczka" [email protected] wrote:
The installer failed but REPL seems to be working.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/rjpcomputing/luaforwindows/issues/114#issuecomment-258598488, or mute the thread https://github.com/notifications/unsubscribe-auth/AADKCV_tmCZMFJ4dbPP219HwRARdBgdkks5q7D8tgaJpZM4KqNFz .
That's all right but still the failure is confusing (especially that things appear to work)
@moozzyk,
I completely agree. I wonder if the VC2005 redist doesn't work in Windows 10. Maybe they built it in now. I have no real testing in Windows 10 yet.
Also could you try to just run this VS2005 redist (https://github.com/rjpcomputing/luaforwindows/releases/download/vc-runtime/vcredist_x86.4053.exe). It is the one that is used during LfW installer.
I have the same problem under win7 64, but it still seems work. but I do not know how to let lua work under CMD.
I encountered the same issue (but wasn't running as admin) and found that the vcredist file (both in the same directory as LuaForWindows_v5.1.5-51.exe and in install\support\ were 0 bytes. Replacing them with the exe @rjpcomputing linked fixed the issue (Win10 Pro x64).
Maybe the installer is failing to download properly?