Subject: Re: Use of opt_ headers
To: Pavel Cahyna <firstname.lastname@example.org>
From: Quentin Garnier <email@example.com>
Date: 08/29/2006 15:45:54
Content-Type: text/plain; charset=us-ascii
On Mon, Aug 28, 2006 at 11:40:39AM +0200, Pavel Cahyna wrote:
> On Mon, Aug 28, 2006 at 10:07:28AM +0100, David Laight wrote:
> > I might also change the defines to be KERNEL_OPT_FOO at the same time.
> that is, for options FOO, config would #define KERNEL_OPT_FOO?
> I think that this is not a good idea. Currently you can define an
> arbitrary kernel macro by just adding the "options" line to the config
> file. The proposed change would destroy that feature.
How come? My reading of David's proposal is that opt_*.h would contain
KERNEL_OPT_FOO definitions. It doesn't mean the way unrestrictive
options are handled has to be changed.
In any case, I'd rather see that feature disappear, promoting the use of
"makeoptions CPPFLAGS+=3D" instead.
Quentin Garnier - firstname.lastname@example.org - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)
-----END PGP SIGNATURE-----