<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 7, 2013, at 12:50 PM, Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Ok, done.<div><br></div><div>I just realized I didn't read Jordan's mail thoroughly and I converted one of the internal docs to Sphinx format, which was against his post. So I will weigh in on that now:</div>
<div><br></div><div style="">There is a distinction between the "docs" and the "website" for each project. For LLVM, the website isn't even open source. For Clang and the Analyzer, it is in a separate directory from the docs. All the websites are currently plain HTML, almost all the code documentation is now Sphinx. It's different, and it might be worth considering making the websites Sphinx too, but a priori they service different goals so having the website and the programming docs in different formats doesn't seem terrible.</div></div></blockquote><div><br></div><div>We were just not clear what were the immediate goals of the clang and llvm conversion and if the complete websites (including plain HTML) are being converted as well as everything in the docs folder. This seems to be the best for constancy, however, it is not clear how much effort is required.</div><div><br></div><div>Currently, most of the analyzer documentation is in plain HTML, so unless there are immediate plans on transitioning HTML to Sphinx/RST, we would continue committing enhancements in HTML. </div><br><blockquote type="cite"><div dir="ltr">
<div style=""><br></div><div style="">It makes total sense to me to have the internal documentation browsable on the websites somewhere, and this is what we do for LLVM and Clang and all the other projects, so I see no reason for the analyzer to be different. Note that its only "exposed" as much as there is a URL for it. You can decide if and when you want to link to it from the website.</div></div></blockquote><div><br></div>Makes sense.</div><div><br><blockquote type="cite"><div dir="ltr">
<div style=""><br></div><div style=""> - Daniel</div><div style=""><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 7, 2013 at 11:19 AM, Daniel Dunbar <span dir="ltr"><<a href="mailto:daniel@zuster.org" target="_blank">daniel@zuster.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Sean,<div><br></div><div>Thanks, I'll start on this now.</div><span class="HOEnZb"><font color="#888888"><div>
<br></div><div> - Daniel</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Jan 5, 2013 at 12:34 PM, Sean Silva <span dir="ltr"><<a href="mailto:silvas@purdue.edu" target="_blank">silvas@purdue.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi ddunbar, in transitioning the analyzer to Sphinx, I'm going to need<br>
some setup on the <a href="http://llvm.org/" target="_blank">llvm.org</a> server as with the other Sphinx<br>
transitions. As background, clang/docs/analyzer is excluded from the<br>
Sphinx build in clang/docs/, and has its own self-contained Sphinx<br>
build.<br>
<br>
So what is needed is to run `make` inside `clang/docs/analyzer/` (no<br>
`-f Makefile.sphinx` since there was no conflicting Makefile in this<br>
directory), then copy `clang/docs/analyzer/_build/html/` to appear at<br>
<<a href="http://clang-analyzer.llvm.org/docs/" target="_blank">http://clang-analyzer.llvm.org/docs/</a>>.<br>
<br>
Thanks,<br>
<br>
-- Sean Silva<br>
<div><br>
On Wed, Jan 2, 2013 at 6:19 PM, Sean Silva <<a href="mailto:silvas@purdue.edu" target="_blank">silvas@purdue.edu</a>> wrote:<br>
</div><div>> On Wed, Jan 2, 2013 at 2:56 PM, Anna Zaks <<a href="mailto:ganna@apple.com" target="_blank">ganna@apple.com</a>> wrote:<br>
>> Would be great to have the analyzer documentation converted, but I don't<br>
>> know if anyone has committed to do the work.<br>
><br>
> In r171424 and r171425 I have set up a basic Sphinx setup for the<br>
> analyzer in docs/analyzer/ (segregated from the rest of clang's docs).<br>
> There is no server-side support though so it doesn't currently affect<br>
> the website.<br>
><br>
> -- Sean Silva<br>
</div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</blockquote></div><br></body></html>