On Thu, May 22, 2008 at 8:08 PM, David Manura <
dm.lua@math2.org> wrote:
The concern was more for extension (of Lua apps and utilities) rather than
embedding. I'm not arguing for the inclusion of internal source files such a
lua.c and lmem.h but rather only what is analogous to the files in the "include"
and "libs" directories in ActivePython (which I think has similar goals to Lua
for Windows).
As a case in point, I needed the LuaGL DLL to run an example, but I didn't have
a binary, so I proceeded to compile that DLL from source. To compile it from
source required having lua.h and luaconf.h around. Now, it's unclear which
version of luaconf.h is compatible with the lua.exe in Lua for Windows since
each build of lua.exe can have a customized version of luaconf.h. So, I grabbed
these files from somewhere else and hoped for the best (probably, it would have
been best to use LuaBinaries, but there are many builds of LuaBinaries too).
Added to the todo list. Good point. By the way, there is a todo.txt and changes.txt that show the items that still need to be done and what has been included.
Also I use LuaBinaries and there really is only one release, as a binary, for Windows. It uses these without any modifications. It also was built using Visual C++ 8.0, so that is the run-time required.
Hm..I got an error that "gl" was nil. Building an opengl.dll and doing "require
'opengl'" resolved it. I also tried some external glut examples (without IUP)
but got crashes (though possibly something in my compile/link wasn't right, as I
didn't find a Makefile in the LuaGL distribution).
