Subject: Re: Use of opt_ headers
To: None <tech-kern@NetBSD.org>
From: Peter Seebach <firstname.lastname@example.org>
Date: 08/28/2006 04:21:53
In message <20060828090727.GP1396@snowdrop.l8s.co.uk>, David Laight writes:
>Code will then have to contain '#if FOO()' which generated a syntax error
>if opt_foo.h isn't defined.
>Any other thoughts/objections before I try to script the required edit?
What is the compelling reason to write two dozen or more different files,
rather than having a single "options.h" header that everyone includes?
Are we worried about dependency checking on changing options, or what? I
haven't built a kernel in years in which I changed any options without a make
clean; does anyone do that still? (I'm not saying they don't; I've just not