On Thu, Apr 4, 2013 at 2:50 PM, steve donovan <steve.j.dono...@gmail.com>wrote:
> Yep, the logic is not right. That's why I'm writing a pure Lua install
> script ...
>
Which is classic rewrite mentality, of course. The Windows case is
complicated by two compilers, and at least two incompatible run-times.
Although generally Windows binary compatibility is really good, Visual
Studio comes with its own runtime, so we have the old LfW standard
(MSVC2005) using msvcr80. MinGW can also link against this - in fact, given
that this MS compiler is hopelessly obsolete, it's the only commonly
available compiler that can do so. It's irritating to have to redistribute
this runtime, so the plain link against the Windows C runtime that MinGW
usually does is a better option.
However, the old runtime still has life in it because the binary Windows
rocks in the repo are built against it. So it's still best for the
compiler-free.
This is all relevant to configuring LR on Windows - that /MW (use mingw)
flag means 'use mingw32-gcc' and does not distinguish between the two
possible runtimes. If installing LR's copy or old Lua for Windows, then I
can be pretty sure that its msvcr80.
When writing the script, I find myself making the assumption that people
actually put things on their path. This may not be always true, but life is
a lot easier then.
steve d.
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Luarocks-developers mailing list
Luarocks-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
