Murray.Cumming@...166... wrote:
But, on sane systems such as debian's apt and RedHat/Fedora's new thingy, and others, you will just install Inkscape and it will take care of the rest. People will not even know, or care, that you use gtkmm.
An alternate way of doing it, if necessary, is linking with -rpath, and just carrying the dependent .so's along with the app in a subdirectory, much like a Windows app often supplies its own DLL's without "installing" them.
If you have ever installed Java on linux, you might notice that it carries many such .so's along with it in its
$JAVA/jre/lib/i386
directory, linked with relative paths. It very rarely has a need for any extra external libs. I think this is sweet.
So just having a /lib subdir with libgtkmm-2.0.so, libglib-2.0.so, libatkmm-1.0.so, ....etc.... would give us the ability to never worry what someone does or does not have installed.
Where I work, we do cross-platform stuff, like for Windows, Solaris, Linux, SGI, you name it. We often need to deliver software like this. We can't expect customers to have recent versions of anything, nor can we expect them to upgrade. For Unixy things, -rpath can be a lifesaver.
Bob