On 2/8/2013 4:07 PM, Stephan Beal wrote:
....
Please forgive my ignorance of lua, but what am i missing here?
....
Sorry, I should have included a list of prerequisite Lua modules. On
Windows, all the prerequisites (and lots more modules) are satisfied by
the Lua for Windows distribution available here:
http://code.google.com/p/luaforwindows/
A quick scan for require statements indicates that I used
* Penlight: http://stevedonovan.github.com/Penlight/
* LuaJSON: http://github.com/harningt/luajson
* LuaBitOps: http://bitop.luajit.org/
over and above modules that are part of Lua itself, or included in the
repository already.
I should add that I had to fix a bug in the version of penlight I used,
but it looks like that fix has been made upstream so it might not be an
issue for you...
* https://github.com/stevedonovan/Penlight/issues/36
Once you get the script running at all, your next hurdle will likely be
making pandoc and a suitable LaTeX available to it as well. Of course,
you can get a lot of mileage out of it by passing the --markdown option
to reporter.lua which will cause it to just save the reports in Markdown
rather than automatically converting them to PDF.
The other fun bit of learning curve will be reading between the lines of
my extremely terse documentation to convert sample.report into something
that does something useful for you... for that, the documentation from
Penlight of the template parser I used might be helpful in addition to
what can be found in readme.md. In this document, you just need to know
that I configured it to use @ in place of #...
* http://stevedonovan.github.com/Penlight/api/modules/pl.template.html
--
Ross Berteig [email protected]
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
+1 626 351 1590 FAX
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
