play pre functions aries programs mem lba other pil

http://blog.csdn.net/yue7603835/article/details/41739085

http://blog.csdn.net/birdflyto206/article/details/49403801

Building Lua on other systems

If you‘re not using the usual Unix tools, then the instructions for building Lua depend on the compiler you use. You‘ll need to create projects (or whatever your compiler uses) for building the library, the interpreter, and the compiler, as follows:

library:

lapi.c lcode.c lctype.c ldebug.c ldo.c ldump.c lfunc.c lgc.c llex.c lmem.c lobject.c lopcodes.c lparser.c lstate.c lstring.c ltable.c ltm.c lundump.c lvm.c lzio.c lauxlib.c lbaselib.c lbitlib.c lcorolib.c ldblib.c liolib.c lmathlib.c loslib.c lstrlib.c ltablib.c lutf8lib.c loadlib.c linit.c

interpreter:

library, lua.c

compiler:

library, luac.c

To use Lua as a library in your own programs you‘ll need to know how to create and use libraries with your compiler. Moreover, to dynamically load C libraries for Lua you‘ll need to know how to create dynamic libraries and you‘ll need to make sure that the Lua API functions are accessible to those dynamic libraries — butdon‘t

link the Lua library into each dynamic library. For Unix, we recommend that the Lua library be linked statically into the host program and its symbols exported for dynamic linking; src/Makefile does this for the Lua interpreter. For Windows, we recommend that the Lua library be a DLL. In all cases, the compiler luac should be linked statically.

As mentioned above, you may edit src/luaconf.h to customize some features before building Lua.

在Windows下編譯Lua