On Tue, Sep 7, 2010 at 19:46, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: > Tom Browder <tom.browder@xxxxxxxxx> writes: > >> Does anyone know if the libstdc++ manual is available in pdf? >> >> I see the xml sources for docbook, but I haven't found a pdf output >> yet. And I'm not sure it's configured to be built. >> >> Someone has some missing pieces because the html is generated by >> docbook from the xml. Not docbook, prince (http://www.princexml.com/). >> Is that product something that needs a volunteer to make happen in the >> gcc build system? Looks like the prince license may be one of the limiting factors (see below). > You should be able to build it by running "make doc-pdf" in the > TARGET/libstdc++-v3 build directory. You need to have some program > called "prince" installed; I'm not sure where that comes from. "prince" is not open source, but a commercial xml/html processor that seems to allow open source projects a non-paid license. From the prince web site (http://www.princexml.com/license/): <quote> 1.1 Non-commercial license If this is a Non-commercial license, Licensee may download, install and use the Software for Non-commercial Purposes on a computer that is accessible to any number of end users. PDF documents generated by the Software include notices that identify the Software. Licensee shall not change or remove these notices or assist or encourage third parties to remove or change such notices. When the Non-commercial license is used to routinely generate documents, a prominent link to the www.princexml.com Web site shall be displayed on the pages from where the generated documents can be fetched, and in a prominent Web page where business partners are listed. If PDF documents are sent as email attachments by Licensee, all email messages must contain the www.princexml.com Web address in the message body. </quote> Sounds to me like converting the libstdc++ doc build process to use DocBook 5 and Apache Fop (both open source projects) would be a good thing and enable the libstdc++ docs to be displayed with all the other manuals. Regards, -Tom Thomas M. Browder, Jr. Niceville, Florida USA
