On Tue, 21 Sep 2004, Bob Jamison wrote:
> I am not sure if this has been agreed upon, but we
> are going to use static linking for all of our C++ dependencies,
> right? In other words, for all of the libs:
> They are ./configured with --enable-static --disable-shared, so that
> subsequent 'pkg-config --libs' calls will return the info needed
> for static linking?
> We need to remove C++ dependencies from the shoulders of our
> users, -especially- since different C++ compilers and different versions
> of the same compiler usually do not mix.
> A way to check such dependencies would be:
> 'ldd inkscape'
> The C++ libs should not be listed.
Afaik, for the linux distros, there has been no such decision to
statically link the C++ libs. Possibly they should, but it would
require further discussion.
For the 0.40 release we discussed waiting on release until gtkmm 2.4, et
al became more widely available. We had distributed with the gtkmm 2.2
last time around, with few problems other than the expected one of some
users not having that package already installed.
For libgc, we've really not discussed how to handle that very much, but
given that the packages I've seen in the wild have not been compiled
with the C++ flag, I think it'd be an excellent candidate to statically
link in, especially since unlike gtkmm it's unlikely to be shared by
very many other apps on the user's machine.
Anyway, if there's further concerns, this'd be a good point to get them