On Tue, Apr 1, 2014 at 11:20 AM, Moose <moose@posteo.de> wrote:
The executable itself is in my case a unit test that links against
the dll
that exposes the functions. The executable itself does not expose
anything.
Microsofts dependency walker shows that the DLL exposes the C
functions all
right. After all, it works when I explicitly load() the DLL.
Then it should work. I agree, if you have LuaJIT you may as well use
the FFI because it is faster and less work to set up. But, are these
functions exported as "extern "C"" - because C++ mangling will mess up
the names. Look to see what the function names actually are.
