This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Conditionalizing the GCC documents
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Cc: gcc at gcc dot gnu dot org, Stan Shebs <shebs at apple dot com>, Bill Cox <bill dot cox at windriver dot com>, Richard dot Earnshaw at arm dot com
- Date: Mon, 11 Mar 2002 18:42:12 +0000
- Subject: Re: Conditionalizing the GCC documents
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> On Tue, 26 Feb 2002, Stan Shebs wrote:
> >> Our company wants to ship GCC docs only for the target architectures
> >> that our customers use. I'd like to submit to the gcc/*.texi files to
> >> make the specific arch support conditional like the GAS manual does.
> > So I'd like to put in a vote not to go down that path. If it's that
> > important to Wind River, then it should be possible for you to maintain
> > this as a local patch.
>
> I thought about this, and came to the same conclusion as Stan, so I
> believe this should be kept a Window River-local patch.
>
> (The crucial question for me, wearing my GCC maintainer hat, is ``How
> does the FSF version of GCC benefit from such a change''?)
I wouldn't object to it being possible to do this, provided:
1) It was possible to build a manual with all optional sections in it
2) The default was to do that.
That would put the onus on people wanting to make cut-down manuals to keep
the optional parts consistent.
R.