This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: RFC on building the header bits
- To: Stephen Webb <stephen dot webb at cybersafe dot com>
- Subject: Re: RFC on building the header bits
- From: Benjamin Kosnik <bkoz at redhat dot com>
- Date: Wed, 14 Mar 2001 10:17:24 -0800 (PST)
- cc: libstdc++ at gcc dot gnu dot org
> I've got a working solution to the problem of picking up the
> ISO-compliant headers on Solaris 8 (or others, if available). The
> catch is, the headers need to be built. I notice the shadow headers
> also need to be built. The shadow headers won't work right now,
> because they are built by the src/Makefile, but required by the
> libsupc++ build, which is a dependency of the src build (you get the
> idea?).
Right.
You can do this at the point of configure.in where we make std_limits.h.
> I've tried a few klever tricks, but automake is being very difficult
> about building header files for you, at least the way we need it done.
> Some built header files are generated directly by the configure script,
> and while inelegant, that will work (you just lose the dependency
> tracking make can bring).
this is what mkcshadow does
> What I'm proposing, and soliciting comments on, is the idea that ALL
> headers in the c/c_std/c_shadow thing get built (with the c_std headers
> just being links or copies from the src to the bld area). To get
> around the automake limitations, I would add a shell script that is
> invoked at confiure time that will generate the target bits from the
> appropriate source (rather than just including the code in the
> configure script). This will make some of the later build
> dependencies a little simpler, and installations will be a little
> simpler, and I can finish this project and move on to something else.
Ok. Try this approach, so that you can post a clean working patch. Once
we can see what you've done perhaps somebody can up with something really
clever.
thanks,
benjamin