Testing Flow
Posted by ewing on 2007-12-26 13:44
Today:
Redid merge with Ken’s original Lua experiment with CVS head. This time it worked.
Also quick implemented the idea I described on the original Kitware CMakeLua wiki page about implementing a public API face in Lua itself as a utility/helper script. Right now, cm.add_library has the ability to handle tables or va-arg lists of files as described on the wiki page.
Need to do:
It would be nice to change the cm_ prefix to put something in a table instead (like cm., or better yet cmake.). Also need to consider if helper script should provide a separate public API or override the C-api. For example, if we provide cmake.add_library in the helper script, should there be a way to directly access the underlying C-api interface (currently cm_add_library)?
The utility script should probably also follow Lua 5.1 module conventions.
It would also be nice to add in lrexlib (and maybe lpeg?) since better regular expressions seems to be a current request on the CMake mailing list.
Issues:
Something like a luaL_require would be handy to (cleanly) prevent the utility script being loaded/run multiple times.
For lrexlib, lpeg, and any other library plugins, we need to find a location relative to the CMake support files to place and find/load the plugins from. Should this go in the Modules section? Or maybe we should just statically link everything?
Major refactoring has been discussed. This probably should be done before I make more changes.
Redid merge with Ken’s original Lua experiment with CVS head. This time it worked.
Also quick implemented the idea I described on the original Kitware CMakeLua wiki page about implementing a public API face in Lua itself as a utility/helper script. Right now, cm.add_library has the ability to handle tables or va-arg lists of files as described on the wiki page.
Need to do:
It would be nice to change the cm_ prefix to put something in a table instead (like cm., or better yet cmake.). Also need to consider if helper script should provide a separate public API or override the C-api. For example, if we provide cmake.add_library in the helper script, should there be a way to directly access the underlying C-api interface (currently cm_add_library)?
The utility script should probably also follow Lua 5.1 module conventions.
It would also be nice to add in lrexlib (and maybe lpeg?) since better regular expressions seems to be a current request on the CMake mailing list.
Issues:
Something like a luaL_require would be handy to (cleanly) prevent the utility script being loaded/run multiple times.
For lrexlib, lpeg, and any other library plugins, we need to find a location relative to the CMake support files to place and find/load the plugins from. Should this go in the Modules section? Or maybe we should just statically link everything?
Major refactoring has been discussed. This probably should be done before I make more changes.
Home / Developer API / Tour / Get a Project - Solutions for Bug & Issue Tracking, Collaboration Tools, Subversion Hosting, Git Hosting
Cmakelua is powered by Assembla.
0 Comments