(Posted as question #123799 on Launchpad) https://answers.launchpad.net/inkscape/+question/123799
For Debian/Ubuntu packaging purposes, it would be preferable for us to build against an external (clean) version of libcroco rather than using the one currently in the Inkscape source-tree. A while ago, someone asked at the Debian bugtracker about this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427946
At the time, it seems that a patched version of libcroco-0.6 was included in the source tree of inkscape-0.45, and that Inkscape could not be built with the upstream version of libcroco. Since then, a lot of changes have been made in Inkscape (including the removal of src/libcroco/README) and there is a new upstream version (0.6.2) of libcroco. Please could someone update us on the situation? Specifically:
* Which version of libcroco is included with Inkscape 0.47/0.48? * Have any changes been made to the bundled library? * Can Inkscape be built successfully using a clean external libcroco?
Thanks,
Alex
2010/9/2 Alex Valavanis <valavanisalex@...400...>:
- Which version of libcroco is included with Inkscape 0.47/0.48?
It was derived from some 0.6.x.
- Have any changes been made to the bundled library?
Yes, there is a generic selection engine added that allows us to use libcroco with our custom XML nodes. We cannot migrate to libxml2 because we are making heavy use of XML tree change notifications, a feature that is not present in libxml2. We could use upstream libcroco if this bug was fixed: https://bugzilla.gnome.org/show_bug.cgi?id=572454
- Can Inkscape be built successfully using a clean external libcroco?
No.
Regards, Krzysztof
participants (2)
-
Alex Valavanis -
Krzysztof Kosiński