C library headers
Nathan Myers
ncm@cantrip.org
Fri May 12 10:58:00 GMT 2000
On Fri, May 12, 2000 at 08:50:31AM +0100, Anthony Williams wrote:
> From: Nathan Myers <ncm@cantrip.org>
> > On Thu, May 11, 2000 at 12:35:42PM +0100, Anthony Williams wrote:
> > > I have been working on a set of headers for the C library
> > > portion, using Nathan's guidelines from
> > > http://www.cantrip.org/cheaders.html which are nearly finished.
> > >
> > > Am I duplicating effort? If not, when I have them finished (next
> > > day or so) how do I submit them?
> >
> > This is very, very good.
> >
> > Note that for the headers to be useful in practice, they probably
> > need the various POSIX and XOPEN extensions found in the glibc
> > headers and similarly girded about with #ifdefs. Patches for glibc
> > headers might be more useful than complete headers.
>
> I thought the idea was to do this in such a way that the system
> headers were used, though this requires sub-included headers to be
> shadowed. I am doing this on Solaris, so the set of sub-included
> headers is probably different than for LINUX.
I'm sorry, Anthony, I misunderstood what you were doing. Most of the
work for "shadow" headers has already been done, and is in the tree
under /shadow, along with scripts mkshadow and inclosure. It just
needs to be finished, including ...
> POSIX and XOPEN stuff (it'll just take a little
> longer :(
There's no problem with staging the work. Send patches for what you
have, and later patches for the rest. We will need to hack up the
configure system to allow us to choose whether to install your
(initially incomplete) shadow headers. When they're done, we can
make that the default if configure doesn't find glibc headers with
the work already done in them.
Nathan Myers
ncm at cantrip dot org
More information about the Libstdc++
mailing list