<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Nov 17, 2013 at 5:17 AM, Sean Silva <span dir="ltr"><<a href="mailto:chisophugis@gmail.com" target="_blank">chisophugis@gmail.com</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"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="im">On Sun, Nov 17, 2013 at 3:50 AM, Mikael Lyngvig <span dir="ltr"><<a href="mailto:mikael@lyngvig.org" target="_blank">mikael@lyngvig.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">It wouldn't take me more than an hour or two to do the format conversion. It is rather trivial, actually. Just say the word and I'm on to it like a starving bee. I guess I should get used to using the Sphinx layout; I'm simply more familiar with the format I use on my own websites.<div>
<br></div><div>Have you guys ever considered making a less formal wiki for LLVM documentation - a place where tiny snippets and tricks could be stored? A place that anybody could contribute to in such a way that only the Wiki editors could accept or reject a proposed change. Kind of like Wikipedia. <a href="http://wiki.llvm.org" target="_blank">http://wiki.llvm.org</a>. If you are short on resources, I'd be happy to volunteer for the task of co-Wiki-editor (this doesn't require as big knowledge of LLVM as you'd think; it is mostly a matter of rejecting attempts to defame the site and such). If any topic in the Wiki became too complex or too important, somebody could get started on writing the appropriate coherent, user-friendly documentation that could be merged into the main branch of documents.<br>
</div></div></blockquote><div><br></div></div><div>Also, I'm not sure how many such "tips and tricks" or "tiny snippets" there can be (and I'm cautious about how quickly they will go out of date). It's honestly probably easier for LLVM developers to edit files in the repository (purely from a workflow perspective).</div>
</div></div></div></blockquote><div><br></div><div>That "Also," at the beginning was a leftover when I switched the paragraph order. Please ignore it.</div><div><br></div><div>-- Sean Silva</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div><br></div><div>My biggest reason for opposing such a wiki is that it is decoupled from the community, which is centered on the mailing lists. A person doesn't have to get on the mailing lists to submit an edit to such a wiki, which means that they won't become part of the community whereas in order for them to contribute to docs/, they have to reach out to the community and send a patch, which is a gateway drug to further involvement.<br>
</div><div class="im"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">
<div>
</div><div><br></div><div><div>What if we renamed the ARM document to "TipsForBuildingOnARM" instead of "HowToBuildOnARM"?<br></div></div></div></blockquote><div><br></div></div><div>We currently don't have an easy way to serve a redirect to the new page, so for the moment we can't rename it (URL's should never break). This is <<a href="http://llvm.org/bugs/show_bug.cgi?id=14714" target="_blank">http://llvm.org/bugs/show_bug.cgi?id=14714</a>>. Actually now that I think about it maybe we can do it with a dummy html file with a <meta> tag with `http-equiv`? Finding a working setup for that is probably a better use of your time than reformatting. One other page that is in dire need of a rename is clang/docs/Tooling.rst, which is actually "choosing the right interface for your application".</div>
<div class="im">
<div><br></div><div>-- Sean Silva</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">
<div><div></div></div><div class="gmail_extra"><br></div><div class="gmail_extra">-- Mikael</div>
<div class="gmail_extra">-- Apprentice LLVM Tech Writer.<div><div><br><br><div class="gmail_quote">2013/11/17 Sean Silva <span dir="ltr"><<a href="mailto:chisophugis@gmail.com" target="_blank">chisophugis@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">
On Sun, Nov 17, 2013 at 12:53 AM, Mikael Lyngvig <span dir="ltr"><<a href="mailto:mikael@lyngvig.org" target="_blank">mikael@lyngvig.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Thanks for spotting those errors! Fixed.<br>
</div><div><br></div><div>If you feel that this doc should be part of the LLVM documentation, perhaps in a revised form, just let me know. I am willing to convert it into reST and also to go through a peer review, but I simply cannot spend hundreds of hours munging about, rewriting, and retesting over and over as I am already busy on other documentation and other sub-projects.</div>
</div></blockquote><div><br></div><div>If it would require a format conversion, it's not a big deal. However, it would be nice to add a link to an appropriate document. Probably just tack it on at the end of HowToBuildOnARM (which should be called AgglomerationOfTipsForBuildingOnARM) with a sentence of description.</div>
<div><br></div><div>-- Sean Silva</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">
<span><font color="#888888">
<div><br></div><div>-- Mikael</div></font></span></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/11/17 Dmitri Gribenko <span dir="ltr"><<a href="mailto:gribozavr@gmail.com" target="_blank">gribozavr@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">On Sat, Nov 16, 2013 at 9:15 PM, Mikael Lyngvig <<a href="mailto:mikael@lyngvig.org" target="_blank">mikael@lyngvig.org</a>> wrote:<br>
> <a href="http://llvm.lyngvig.org/Articles/How-to-Setup-an-Arch-Linux-Buildbot-for-LLVM" target="_blank">http://llvm.lyngvig.org/Articles/How-to-Setup-an-Arch-Linux-Buildbot-for-LLVM</a><br>
<br>
> Notice: You only need Ninja for the test build; none of the official LLVM builders use Ninja as far as I know.<br>
<br>
My buildbots use ninja.<br>
<br>
> Please notice that you must specify the absolute path to ninja, otherwise CMake can't figure out where it is located.<br>
<br>
Strange, I never had to do this. I just put 'ninja' binary into my PATH.<br>
<br>
> pushd llvm-trunk/tools > /dev/null<br>
<br>
This does not look correct to me, because you are not entering the<br>
'clang' directory. Similarly, for compiler-rt below.<br>
<span><font color="#888888"><br>
Dmitri<span><font color="#888888"><br>
<br>
--<br>
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if<br>
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com" target="_blank">gribozavr@gmail.com</a>>*/<br>
</font></span></font></span></blockquote></div><span><font color="#888888"><br></font></span></div>
</div></div></blockquote></div><br></div></div>
</blockquote></div><br></div></div></div></div>
</blockquote></div></div><br></div></div>
</blockquote></div><br></div></div>