You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a longstanding historical problem in Windows-land, where because different binary distributions have used different library names, sometimes executables and other libraries link against lua51.dll and sometimes they use lua5.1.dll and then this causes problems. The general solution is have a proxy dll that forwards calls.
See, for instance: http://www.freelists.org/post/luajit/The-dreaded-newbie-questions,10 http://luabinaries.sourceforge.net/manual.html
Can you make the luapower build also link a small proxy lua5.1.dll that forwards all calls to lua51.dll?
The text was updated successfully, but these errors were encountered:
TBH I don't like these kinds of hacks. If I were you I'd learn how to make custom build scripts for those libs and rebuild them to link against the right library.
There's a longstanding historical problem in Windows-land, where because different binary distributions have used different library names, sometimes executables and other libraries link against lua51.dll and sometimes they use lua5.1.dll and then this causes problems. The general solution is have a proxy dll that forwards calls.
See, for instance: http://www.freelists.org/post/luajit/The-dreaded-newbie-questions,10
http://luabinaries.sourceforge.net/manual.html
Can you make the luapower build also link a small proxy lua5.1.dll that forwards all calls to lua51.dll?
The text was updated successfully, but these errors were encountered: