Am 27.05.2015 um 01:41 schröbte XIAO Qi: > 2015-05-26 2:39 GMT+02:00 Philipp Janda <siffie...@gmx.net>: >> >> You already mentioned unit tests (or system tests), and I see that the >> GSoC page also lists automatic documentation generation using tools like >> LDoc, lut, Docco, Doxygen, naturaldocs, etc. Those two are the important >> ones for me, but I'll throw in another idea: There are some source to >> source transformation tools (e.g. LuaMacro, Moonscript, Objective Lua, >> MetaLua, some amalgamation tools, or even plain luac). It would be nice >> to be able to transform at build time and install the precompiled files >> instead of the original source code. Of course there are also some >> programming languages that generate C code as output (but I don't care >> much about those) ... >> > > Thanks for the idea. Correct me if I am wrong, but this is only > relevant to the builtin build backend right? For other backends you > can already do this manually.
Yes, but you can also run tests or generate documentation from a Makefile (e.g. lua-apr[1] does this, and it also generates[2] a new C source file containing error number definitions extracted from a library header. Packages using some form of FFI might want to do similar things -- Alien even has a Lua script[3] for this.) Philipp [1]: https://github.com/xolox/lua-apr [2]: https://github.com/xolox/lua-apr/blob/master/etc/errors.lua [3]: https://github.com/mascarenhas/alien/blob/master/src/constants ------------------------------------------------------------------------------ _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
