> On Jun 11, 2021, at 11:50 AM, Joseph Myers <jos...@codesourcery.com> wrote: > > ... > > "make" at top level should build all the info manuals and man pages, as at > present (if a suitable Sphinx version is installed), and "make install" > should install them, in the same directories as at present. > > "make html" at top level should build all the HTML manuals, and "make > install-html" should install them. > > "make pdf" and "make install-pdf" at top level should work likewise. > > "make install-html" and "make install-pdf" should put things under > $(DESTDIR)$(htmldir) and $(DESTDIR)$(pdfdir) as at present. And in addition, it would be nice to have additional make <foo> and make install-<foo> targets for other output formats that Sphinx can generate for us, at least some of them. "epub" comes to mind as an example I would like to have. paul
- Re: GCC documentation: porting to Sp... Joel Sherrill
- Re: GCC documentation: porting ... Joseph Myers
- Re: GCC documentation: porting ... Martin Liška
- Re: GCC documentation: porting ... Joseph Myers
- Re: GCC documentation: porting ... Martin Liška
- Re: GCC documentation: porting to Sphinx Joseph Myers
- Re: GCC documentation: porting to Sphinx Martin Liška
- Re: GCC documentation: porting to Sphinx Joseph Myers
- Re: GCC documentation: porting to Sphinx Martin Liška
- Re: GCC documentation: porting to Sp... Joseph Myers
- Re: GCC documentation: porting ... Koning, Paul via Gcc
- Re: GCC documentation: porting ... Martin Liška
- Re: GCC documentation: porting ... Joseph Myers
- Re: GCC documentation: porting ... Martin Liška
- Re: GCC documentation: porting ... Martin Liška
- Re: GCC documentation: porting ... Martin Liška
- Re: GCC documentation: porting ... Arnaud Charlet
- Re: GCC documentation: porting ... Martin Liška
- Re: GCC documentation: porting ... Arnaud Charlet
- Re: GCC documentation: porting ... Martin Liška
- Re: GCC documentation: porting ... Martin Liška