![[NLUUG]](/opmaak/images/nluug-ds-200x143.gif)
Current directory: /ftp/os/BSD/NetBSD/NetBSD-release-10/src/external/cddl/osnet/sys/sys/
|
|
Welcome to ftp.nluug.nl Current directory: /ftp/os/BSD/NetBSD/NetBSD-release-10/src/external/cddl/osnet/sys/sys/ |
|
Contents of README:
# $NetBSD: README,v 1.2 2022/05/03 12:09:19 jkoshy Exp $
General guidelines for system wrapper header maintainance.
There are two kinds of system header files:
1. "infrastructure" headers that provide base definitions and
other stuff that other headers use (systm.h)
2. "feature" headers that provide a specific feature (proc.h).
The solaris ones generally augment ours; the template should be:
solaris/foo.h:
#ifndef SOLARIS_SYS_FOO_H
#define SOLARIS_SYS_FOO_H
/*
* This include should not be in #ifdef KERNEL.
* It is the job of the header itself to protect itself.
* Unless Solaris exposes this header in userland, where
* it is probably better to fix our header...
*/
#include_next <sys/foo.h>
/* More Solaris-specific definitions */
#endif /* SOLARIS_SYS_FOO_H */
Now there cases where the solaris headers expose more stuff than ours,
so we need to include more of our system headers from theirs. When that
happens the rule should be that:
Their infrastructure headers should not include our feature headers,
but can include our infrastructure headers, otherwise we end up with
circular dependencies. Violations to the rule should be kept to a minimum
and tested carefully.
In the general case, if we want the augmented symbols we should include
the solaris ones first in the search path.
|
Name Last modified Size
Parent Directory -
CVS/ 27-Nov-2024 04:07 -
README 03-May-2022 14:09 1.4K
sha2.h 28-Feb-2010 18:22 326
NLUUG - Open Systems. Open Standards
Become a member
and get discounts on conferences and more, see the NLUUG website!