This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [libstdc++,doc] How to actually do this?
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Thu, 17 Sep 2009 12:53:30 -0700
- Subject: Re: [libstdc++,doc] How to actually do this?
- References: <alpine.LSU.1.99.0909121846150.32170@acrux.dbai.tuwien.ac.at>
> Here is one patch that I have created, and now I wonder whether
> that's all I can just commit this or, if not, what further steps
> I need to take.
Just commit it, and it will show up the next time the manual HTML is
regenerated.
The on-line documentation (ie gcc.gnu.org) displays the last checked-in
version of the XML docs that have been rendered to HTML, which can be
generated yourself via the 'make doc-html' command. (Which is what
vendors use to package the docs for distribution.) Then this is copied
from the build directory to the source directory into the
libstdc++-v3/src/html folder, and checked in. Then I use the script in
my home folder on gcc.gnu.org, see update_web_docs_libstdcxx_svn.
It would be nice to have the gcc.gnu.org website track changes and
generate the HTML in a more automated fashion. Suggestions welcome...
> Is there any documentation on how to change libstdc++ documentation?
http://gcc.gnu.org/onlinedocs/libstdc++/manual/documentation_style.html
> 2009-09-12 Gerald Pfeifer <gerald@pfeifer.com>
>
> * doc/xml/manual/appendix_contributing.xml: Adjust link to
> coreutils.
OK.
-benjamin