On Fri, Aug 8, 2008 at 12:19 PM, Ralph Hempel
<rhempel@hempeldesigngroup.com> wrote:
Steve Donovan wrote:
I may be missing things but why does vcredist_x86.exe have to be involved?
Lua as a DLL and a number of modules under cygwin but using
the -mno-cygwin option.
I then moved all of the resulting binaries to an absolutely
clean (fresh install) Win2K machine, which is actually
a VMware instance.
Lua seems to run fine - without the hassle of downloading
a new C runtime.
Sure because you used GCC on Windows. That uses the VC6 runtime which is part of the os from 200 on. I would MUCH rather use MinGW GCC but the LuaBinaries didn't, so I work around it the best I can.
Is the new runtime required on Vista, or is it required simply
because LfW is using VC2005 to compile Lua and its modules?
We are using LuaBinaries and as such I am not compiling anything. And they choose to only build using VC2005. And since we use VCs005 the runtime must be installed on that machine. For the full story read this [1]. This is very complicated and I feel like this is the only option Microsoft gives to developers. Please give feedback if there is a better way.
