Windows 64-bit import library

Jordan Wilson wilsonjord at gmail.com
Sun Jul 22 22:35:48 UTC 2018


On Friday, 20 July 2018 at 05:12:05 UTC, Mike Parker wrote:
> On Friday, 20 July 2018 at 04:31:38 UTC, Jordan Wilson wrote:
>
>> I don't have MSVC, so I built it using mingw, which generated 
>> a .a lib.
>> I shall google some more, as I understand it DMD -m64 uses 
>> Mingw libs as a fall back when MSVC not found, I compiled Lua 
>> using mingw, I can't be too much further away from being able 
>> to link in a 64-bit lua import lib in a 64-bit DMD compiled 
>> program...
>
>
> In that case, you may be better off using the DerelictLua 
> binding [1] so that you can avoid the link-time dependency and 
> just load the Lua DLL manually at runtime via 
> `DerelictLua.load` [2]. Then it doesn't matter which compiler 
> the DLL was compiled with or which toolchain you use to compile 
> your app. Version 2.0.0-beta.2 (master and 2.0 branches) binds 
> to Lua 5.3 (don't let the beta tag scare you -- it's stable). 
> If you need Lua 5.2 instead, version 1.3.0 binds to it.
>
> [1] https://code.dlang.org/packages/derelict-lua
> [2] https://github.com/DerelictOrg/DerelictLua

Ah I think you have indirectly reminded me what the problem could 
be, the luaD wrapper that's available is for 5.1 I think (I'm 
trying to link lua 5.3).

Your binding did work quite well, but I think I'll try again 
using lua 5.1, so I can keep using luaD.

Thanks,

Jordan


More information about the Digitalmars-d-learn mailing list