On Fri, Jan 18, 2013 at 11:07 PM, Ross Berteig <[email protected]> wrote:
> Both MinGW and MSVC have worked for me in the past. For my last build (ca. > v1.24), I wanted to turn JSON support on, and that required a bunch of fuss > and bother to get working, IIRC. > i've got some built notes from Tim Ryan here to try to make that simpler, but i don't have a Windows environment and know nothing about nmake syntax, so i haven't got makemake.tcl/Makefile.msc patched yet. > When I build myself a v1.25 real soon now, I'll try to document and feed > back the patch I had to make to the JSON library to get it to compile at > all. > Please do :). > When an "official" windows binary is eventually provided for 1.25, I would > like to respectfully request that it be configured to include ...Windows > app deployment, turning on the JSON features does not change the fact that > fossil.exe is tiny and has next to no installation requirements, > consequences, dependencies, or issues. > :). Last summer Richard told me we could turn JSON on by default once things like unit tests and fuzz tests have been written to make sure that API introduces no security holes, back doors, or other maliciousness (in case you don't know this, i added the JSON support). Shortly after that my health tanked and i have done very little coding since then, so that hasn't happened. Any support i can get from users to help move that along would be extremely appreciated. > My personal use case for JSON support is a tool I wrote to use internally > to produce a PDF showing ticket reports and the full text of all (or mostly > all) tickets. i would also be thrilled to get feedback from experienced users regarding which JSON APIs "are not optimal," so that it can be tweaked to suit. LuaLaTeX. This makes it easy (or at least easier) to include a report of > issues related to a release in a companion document. If there is interest, > I'd be happy to make that tool available as soon as I get the time to > package and document it a tad more. i'd be interested to see (in detail) what you're doing with the JSON API. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
