On 2005-09-23, Peter O'Gorman <[EMAIL PROTECTED]> wrote:
> I have no statistics for how many shared libraries are written in c++ but do
> not take advantage of the standard c++ library, at a guess I'd say that the
> majority use some libstdc++ features.
It's perhaps worth noting that not linking libstdc++ to a library that
requires it means it fails to dlopen() - a fatal error. Whereas linking
libstdc++ to a library which only needs libsupc++ just means that it is
linked to a shared library containing more than it needs (AIUI,
libsupc++ is just a very cut down version of libstdc++).
Linking to libstdc++ when you could get away with libsupc++ is
essentially irrelevant if you're running any other dynamically linked
C++ programs. In fact it's probably slightly better if everything uses
libstdc++ than some use libsupc++!
To me defaulting to C++ pulling in libstdc++ makes most sense, probably
with an ability to override for the minority who don't require it and
care.
Cheers,
Olly
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
