On Wed, 21 Nov 2007 22:08:31 +0100, J.B.C.Engelen@...1578... wrote:
This has not been tested though, so probably needs work. Static linking was what I started out with in LPE development, but when LPE moved to trunk, we chose for having our own copy of 2geom because of frequent 2geom updates caused by progressing LPE dev. Now the situation is different. (static linking would make new lib2geom releases useless for released Inkscape right?)
Dynamic linking wouldn't be much help either -- like many STL-style C++ libraries, a lot of stuff is inlined from headers. Minor changes to interface (or even simply implementation) can easily mean binary incompatibilities.
However, one thing which I think would be very helpful to do now is if we can disentangle Inkscape's copy of lib2geom from the Inkscape build system. That way, the 2geom tree can be an exact copy of a 2geom snapshot (rather than the manually modified copy it is now), and we have a better migration path to using an out-of-tree 2geom.
-mental