This is the mail archive of the
libstdc++@sources.redhat.com
mailing list for the libstdc++ project.
cleaning up header install, 1
- To: libstdc++ at sources dot redhat dot com
- Subject: cleaning up header install, 1
- From: Benjamin Kosnik <bkoz at redhat dot com>
- Date: Tue, 31 Oct 2000 14:42:19 -0800 (PST)
just archiving this
experiments along these lines failed, but when the new automake comes
out, somebody should try it again.
-benjamin
---------- Forwarded message ----------
Date: Thu, 12 Oct 2000 12:48:23 -0700
From: Benjamin Kosnik <bkoz@redhat.com>
To: tromey@cygnus.com, aoliva@cygnus.com, bkoz@cygnus.com
Subject: missing install dir bits
Hey.
I got all the build problems referred to in yesterday's email fixed
with the exception of this includes madness. I've tried what you
outlined (Tom), and have had no luck.
Here's the situation:
libstdc++-v3/include/
has the following sub directories
backward
bits
c
c/bits
c_std
c_std/bits
c_std/sys
ext
std
I'd like to install files from each of these locations into
$(prefix)/include/g++-v3/*. (Things that are in
libstdc++-v3/include/c/foo should be in $(prefix)/include/g++-v3/foo
and things that are in libstdc++-v3/include/c/bits/foo.h should be in
$(prefix)/include/g++-v3/bits/foo.h)
In addition, to make things even more complicated, I have files symlinked into
$(top_builddir)/bits/bar
that need to be installed in
$(prefix)/include/g++-v3/bits/bar
I have been unable to come up with a solution that deals with all this
convoluted directory naming and renaming.
So, my questions for you both are:
1) is an elegant solution possible with net-release-automake/autoconf
2) is any solution possible with the above
If yes, possible strategies would be appreciated.
thanks,
benjamin