<br><br><div class="gmail_quote">2010/11/5 Charles Lepple <span dir="ltr"><<a href="mailto:clepple@gmail.com">clepple@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Nov 5, 2010, at 7:05 AM, Charles Lepple wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
On Fri, Nov 5, 2010 at 3:57 AM, Arjen de Korte <<a href="mailto:nut%2Bdevel@de-korte.org" target="_blank">nut+devel@de-korte.org</a>> wrote:<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
We already have '--with-doc=auto' on the configure commandline, so this<br>
isn't needed. Howevere, there seems to be a problem interpreting the<br>
versions returned by the AsciiDoc tools (from the r2672 Debian-etch build,<br>
similar for the other buildbots):<br>
</blockquote>
<br>
OK, I think I'm caught up on the version comparison thread.<br>
<br>
I think my confusion was that I was looking at the "configure" step,<br>
which really is only needed so we have a makefile with the "make<br>
distcheck" target. I forgot that the parameters could be different<br>
between the two.<br>
</div></blockquote>
<br>
Since the "asciidoc" step (currently "make website") uses the parameters from the first ./configure invocation, I added "--with-doc=auto" there, too.<br></blockquote><div><br>the website target is independent from the with-doc option. we simply rely on AsciiDoc detection to enable these rules.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
In theory, we could extract the generated documentation from the tarball generated by "make distcheck", but that would only be the manuals, not the website.<br></blockquote><div><br>not a problem since the website target is purely for internal use.<br>
it's currently linked to buildbot, but only for the rewrite stage.<br>once completed, we'll move out the website generation, and only keep the doc generation under control<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hopefully the rebuild of r2674 will put the documentation links back on the waterfall.</blockquote></div><br>hopefully, yes ;-)<br><br clear="all">cheers,<br>Arno<br><br>