We do use the pod files, but I don’t think we are too attached to that system. Switching to Sphinx seems fine to me.
> On Jun 13, 2015, at 2:25 PM, Dmitri Gribenko <[email protected]> wrote: > > On Fri, Jun 12, 2015 at 2:47 PM, Sean Silva <[email protected]> wrote: >> >> >> On Fri, Jun 12, 2015 at 2:01 AM, Andrew Wilkins <[email protected]> wrote: >>> >>> In http://reviews.llvm.org/D10304#185908, @silvas wrote: >>> >>>> Clang's man page is the only thing that is generated like this. The rest >>>> use Sphinx's manpage output. >>> >>> >>> @chandlerc given the above, do you still want me to create a >>> macro/function? I'm not deeply involved here, so grain of salt, but I think >>> it'd be better to converge on one documentation tool (Sphinx) than to >>> perpetuate use of multiple formats (Sphinx & pod2man, and whatever else >>> there may be). I could look at rewriting the clang.pod file in Sphinx, and >>> then use Sphinx in CMake. Is that a reasonable change? >> >> >> I would support converting the clang manpage to Sphinx. Dmitri, IIRC Apple >> generates their shipping clang manpage from the pod documentation; do you >> know who is the right point of contact so that we can make sure that you >> guys smoothly transition to generating it with Sphinx? > > Using Sphinx in our build system might be a challenge. Adding Chris > Bieneman and Chris Matthews. > > Dmitri > > -- > main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if > (j){printf("%d\n",i);}}} /*Dmitri Gribenko <[email protected]>*/ _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
