[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Proxy DLL for Lua 5.1; can't get it to work with statically linked liblua
- From: Ulrich Schmidt <u.sch.zw@...>
- Date: Wed, 27 Nov 2013 21:41:35 +0100
Your Error looks like, some entry point in your exe cant be found. I
read your mail in a way, you pulled your externals for the proxy-dll out
of lua51.dll. I think it is the wrong approach. my steps was:
1. compile the exe with statically linked runtime and
__dllextported library functions.
(your mails sounds like you did this already successfully.)
2. run "mkproxy myexe.exe lua51" to create the lua51.dll and lua51.lib
3. optional: compile your modules against the new lua51.lib
Am 27.11.2013 18:48, schrieb Paul K:
Why not change the Value of local var reallib in mkforwardlib.lua?
Let it point to your exe, before you call the link command in mkforwardlib.lua
This way the proxy-dll will point to your .exe.
As I describe in my response to Jerome, I tried that, but got "The
procedure entry point lua.exe.luaL_argerror could not be located in
the dynamic link library lua51.dll." (I tried with and without the
I modified mkforwardlib.lua for my scenario. and attached it to this mail. You need to call it inside a Widows SDK command window. It uses dumpbin.exe to read the exports from <param1> and writes <param2>.dll and <param2>.lib using lib.exe.
Thank you for the script; I tried the DLL that was generated, but got
exactly the same error as above when I tried then to load a module
linked to that proxy: "The procedure entry point lua.exe.luaL_argerror
could not be located in the dynamic link library lua51.dll."
Do you have a proxy library compiled against lua.exe that I can test
with (probably off-list)? Thank you.
Ulrich Schmidt, 08060 Zwickau, Werdauer Str. 90
Tel.: +49 (172) 7928 968