Let me just complement with something we did for Lua for
Windows. The LuaBinaries DLL today do not have the manifests embedded. And we
had some minor problems that were best solved if they had. So I build a custom
DLL for Lua for Windows to have some feedback on this issue. But the
LuaBinaries DLLs are not dynamically loaded, so it is not the same problem
reported by Ryan.
I was just ready to release the next IUP version including the
manifests. I think it is a good idea that modules developed with VC8/VC9 have
their manifests embedded. This explicitly says to the system what RTL DLL you
This problem needs to be further investigated. So far I
understood that the problem occurs only when using the “lua.exe”
executable in an environment that does not have the mscvr80.dll installed on
the Windows repository, right?
[mailto:email@example.com] On Behalf Of RJP Computing
Sent: terça-feira, 5 de agosto de 2008 21:10
To: Lua list
Subject: Re: system error 14001 and vcredist_x86.exe
On Tue, Aug 5, 2008 at 7:57 PM, David Burgess <firstname.lastname@example.org> wrote:
The MS tool depends.exe, the dependency walker will
tell you which
dependent DLLs are not being loaded.
I found out how to solve this issue. The developers are embedding the manifest
into the dll and if they just leave it out then Windows has no problem using
these external C modules. So I think this needs to be known by all Windows
VC8.0 developers to turn that setting off. If you leave it on, then Lua will
not be able to late-load the dll without the vcredist_x86.exe. I found out that
the IUP developers already leave there manifests out and that is why they
worked so well.
I saw a recent thread about the vc run-time and I think what I just found needs
to be disscussed. Thoughts?