lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]


Hi Shmuel,

Can you try running with the executables from my project (just as an experiment) they link to MSVCRT.DLL

It's not that I recommend them, I'm just curious whether they would work in your situation. Just gather a bit of testing :)

https://github.com/malkia/ufo/tree/master/bin/Windows/x64

I provide .dll (lua51.dll), .pdb, import .lib, and also static one.

All compiled against MSVCRT.DLL.

(One thing that would not work is file offsets bigger than 32bits, so don't use it if you rely on it).

I've also recompiled with 5.2 compability (not full, but gets lots of the cool stuff from thew new lua).

Thanks!

On 4/19/2012 1:14 PM, Shmuel Zeigerman wrote:
On 19/04/2012 20:24, Mike Pall wrote:
Shmuel Zeigerman wrote:
Another question please: is there a way to build LuaJIT with the
Windows SDK "statically" so that it wouldn't depend on msvcr100.dll?

I haven't tested this, but try replacing /MD with /MT in
msvcbuild.bat.

Thanks Dimiter and Mike, it worked.

But ... you realize, you won't be able to load any C modules
anymore? Because they'll need to link to the DLL and AFAIK that
doesn't mix well with an embedded static copy of the library.

You may want to consider shipping the VC++ runtime redistributable
installer with the application. Or use MinGW and link against
msvcrt.dll (not an option for Windows/x64).

The problem *is* Windows/x64. I was hoping to get the working system
without the redistributable run-time. I tried to run LuaJIT (built with
the Windows SDK, both statically and dynamically) and got crashes with C
modules linked against msvcrt.dll. For example:
local m = require"lpeg"
m.match(m.V(1)) --> crash

Thanks for your help.