Re: PATCH: new script gcc/doc/install.texi2html

[Mark Mitchell <mark at codesourcery dot com>]

>>>>> "Gerald" == Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:

    Gerald>   SOURCEDIR=/here/is/checked-out-gcc/doc/
    Gerald> DESTDIR=/here/is/the/tree/to/build/the-tarball-from/
    Gerald> $SOURCEDIR/install.texi2html

I would prefer to have this become part of the normal build process.

The basic model in the gcc_release script at this point is that you
check out the sources, do a build (which creates additional stuff in
the source directory, like c-parse.c), and then creates tarballs based
on the (updated) source directory.

If the generated HTML files should go in the source tarballs, then the
way to accomplish that is to make running this script part of `make
bootstrap'.  That seems pretty sensible to me; we might as well build
all the documentation as part of `make bootstrap'.  It doesn't take
long, and it's not like it's very big; the .info files add up to about
30K.

What do you think about that?

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com