<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I think we have decided we will be able to do this. Please go ahead.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 15, 2015, at 4:10 PM, Andrew Wilkins <<a href="mailto:axwalk@gmail.com" class="">axwalk@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_quote"><div dir="ltr" class="">On Tue, 16 Jun 2015 at 06:55 Chris Matthews <<a href="mailto:chris.matthews@apple.com" class="">chris.matthews@apple.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have been informed that it may take some doing to get Sphinx into our build environment. Can you give me a few days to investigate?<br class=""></blockquote><div class=""><br class=""></div><div class="">No problem. Thank you.</div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> On Jun 13, 2015, at 2:25 PM, Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com" target="_blank" class="">gribozavr@gmail.com</a>> wrote:<br class="">
><br class="">
> On Fri, Jun 12, 2015 at 2:47 PM, Sean Silva <<a href="mailto:chisophugis@gmail.com" target="_blank" class="">chisophugis@gmail.com</a>> wrote:<br class="">
>><br class="">
>><br class="">
>> On Fri, Jun 12, 2015 at 2:01 AM, Andrew Wilkins <<a href="mailto:axwalk@gmail.com" target="_blank" class="">axwalk@gmail.com</a>> wrote:<br class="">
>>><br class="">
>>> In <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_D10304-23185908&d=AwMFAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=BSqEv9KvKMW_Ob8SyngJ70KdZISM_ASROnREeq0cCxk&m=nto-1RApbtX9h4ni6l6kDrDBi5RpdbBPtnbkfd50y1k&s=x6nuATr941enemiALzv-VPTJXyrSEwboHgKvfaofwW4&e=" rel="noreferrer" target="_blank" class="">http://reviews.llvm.org/D10304#185908</a>, @silvas wrote:<br class="">
>>><br class="">
>>>> Clang's man page is the only thing that is generated like this. The rest<br class="">
>>>> use Sphinx's manpage output.<br class="">
>>><br class="">
>>><br class="">
>>> @chandlerc given the above, do you still want me to create a<br class="">
>>> macro/function? I'm not deeply involved here, so grain of salt, but I think<br class="">
>>> it'd be better to converge on one documentation tool (Sphinx) than to<br class="">
>>> perpetuate use of multiple formats (Sphinx & pod2man, and whatever else<br class="">
>>> there may be). I could look at rewriting the clang.pod file in Sphinx, and<br class="">
>>> then use Sphinx in CMake. Is that a reasonable change?<br class="">
>><br class="">
>><br class="">
>> I would support converting the clang manpage to Sphinx. Dmitri, IIRC Apple<br class="">
>> generates their shipping clang manpage from the pod documentation; do you<br class="">
>> know who is the right point of contact so that we can make sure that you<br class="">
>> guys smoothly transition to generating it with Sphinx?<br class="">
><br class="">
> Using Sphinx in our build system might be a challenge. Adding Chris<br class="">
> Bieneman and Chris Matthews.<br class="">
><br class="">
> Dmitri<br class="">
><br class="">
> --<br class="">
> main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if<br class="">
> (j){printf("%d\n",i);}}} /*Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com" target="_blank" class="">gribozavr@gmail.com</a>>*/<br class="">
<br class="">
</blockquote></div></div>
</div></blockquote></div><br class=""></div></body></html>