-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSVCR80.dll issue #22
Comments
btw msvcr80.dll is inside the luarock installation (windows), so maybe you can add this to windows dlls. other solution would be to build lua-enet on windows with msys2 (MINGW32) |
hmm, good to know. I'll try it, maybe it'll work, who knows.. |
oh god!! so do you want to know what was the problem? I downloaded the LuaRocks source package that includes a built Lua5.1, replaced lua5.1.dll in the game and guess what. It works! edit: it's quite interesting that i tried quite literally every single thing but looking at luarocks never got me thinking to also try it... |
I am new to lua, gcc and other building stuff related to lua libraries. Try to remember or add a file to know, which LuaRocks version was used, might be necessary in future :) |
I'm not sure what could be the problem, but i'm facing a weird issue with lua-enet. I'm adding multiplayer support to one old C++/SDL game and i was using luasockets before which was working just fine but i wanted to try lua-enet. I'm developing it using Wine on macOS because the game was only for Windows. It's working there using Wine just fine, both client and server connects, all works as it should but i have problems getting it to work on Windows natively.
I either get a MSVCR80.dll not found error there or if i put the C++ runtime dll next to lua5.1.dll and other stuff then it shows
R6034 An application has made an attempt to load the C runtime library incorrectly.
error.I think that recompiling could help, but i wanted to ask first before compiling it myself.
require "enet"
in lua5.1.exe works just fine and also client/server works that wayThe text was updated successfully, but these errors were encountered: