[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Adding module+DLL to Lua for Windows (LfW)
- From: Jerome Vuarand <jerome.vuarand@...>
- Date: Wed, 9 Dec 2009 11:29:01 +0100
2009/12/8 Doug Rogers <doug.rogers@elbitsystems-us.com>:
> Doug Rogers wrote:
>> ... I had remembered a more recent discussion, but the latest
>> message that I found using the lual-l archive search was:
>> http://lua-users.org/lists/lua-l/2008-08/msg00298.html
>
> Also relevant: http://lua-users.org/lists/lua-l/2008-09/msg00077.html
>
> That page says "LfW has standardized on MSVCR80.DLL", but the main LfW
> page still says its "modules all depend on the MSVC++ 2005 runtime library."
>
> Perhaps I'm revealing too much of my ignorance of Microsoft compilers
> and run-times!
VC versions and release year don't match in regards to numbers (2002
is 7.0, 2003 is 7.1, 2005 is 8.0, 2008 is 9.0). Things get even more
complicated if you take into account special VC versions released with
some platform SDKs and the DDKs.
One way to avoid problems with libc runtimes on windows is to link
them statically. I did that on one of my projects and it can greatly
simplify deployment. It slightly increases DLL sizes, but that's still
reasonnable (iirc lua51.dll grew from 160k to 250k or so).