This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] build info files in $(docbuilddir)
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Brendan Conoboy <blc at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: 08 May 2002 19:47:55 -0300
- Subject: Re: [PATCH] build info files in $(docbuilddir)
- Organization: GCC Team, Red Hat
- References: <20020508202223.GA21965@redhat.com>
On May 8, 2002, Brendan Conoboy <blc@redhat.com> wrote:
> Instead of building them in the gcc/doc directory, it builds
> them in $(docbuilddir).
While I like the patch, the macro name is a bit unfortunate since it
gives the impression that it is in the build dir, as opposed to what
we use that is the src dir.
What I'd really like is to have a way to get all files that are
currently generated in the source tree to be optionally generated in
the build tree, at a single configure option or so, say
--enable-srcdir-readonly or so, so that one can have bison- and
info-generated files in the build tree as opposed to the source tree.
I'll take care of that (at least for the info part, for now).
As for the name of the macro, it should be something that doesn't give
the impression of being in neither the source nor the build tree.
Unfortunately, the most natural macro name for this, infodir, is
already taken as the infodir installation directory, and infobuilddir
would bias the name to the build tree, which is what I dislike. I
pondered about it for a while, but couldn't think of anything I
liked, so I'm now open to suggestions. Ideas?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer