Re: How to avoid DLL hell?

[Axel Kittenberger <axkibe@...>]

> It sounds like an "environmental" problem rather than a problem with
> Lua.  How do _other_ infrastructures cope with this in windows?

Agree this is a windows problem. This is IMHO the biggest weakness of
windows, it has no DLL versioning. All people do nowadays is coding
the version into the name of the dll. like microsoft itself e.g.
delivering "mfc42.dll" for the version 4.2 of its fondation classes.
And there is no way to link simply to "the newest version". What all
sane software on windows does, is to provide an installer that comes
with and installs all the libraries you need with it. Thats what I'd
suggest for you. Or just link statically.

On Mon, Nov 22, 2010 at 2:05 AM, Miles Bader <miles@gnu.org> wrote:
> Nick Gammon <nick@gammon.com.au> writes:
>> I don't want to sound negative. I love Lua. I think it's great. But I
>> just don't see how I can get people to do stuff like "replace core.dll
>> and core.dll by core.dll and core.dll" in certain directories, or it
>> will randomly crash every hour when it goes to look up a web page.
>
> It sounds like an "environmental" problem rather than a problem with
> Lua.  How do _other_ infrastructures cope with this in windows?
>
> [A different set of paths for different Lua versions certainly sounds
> necessary, but since installation details are outside of the Lua core's
> provenance, I guess there's not so much the core can do.]
>
> -Miles
>
> --
> Liberty, n. One of imagination's most precious possessions.
>
>