I've now done a couple of builds and DESTDIR installs of 0.92pre3 : the dependencies (for gtk2) seem to be the same as for 0.91, at least on (BLFS-7.10)¹ x86_64 linux.
But there are a few things which puzzle me - I really don't grok cmake, but at least inkscape now builds fine with a separate build dir in the conventional cmake manner. But I looked at the files to work out what options were available, and from the claimed defaults I guessed I might have to turn off a few (gnome_vfs, libcdr, libvisio, libwpg) - but in fast those were all correctly turned off without any action on my part.
That makes me even more surprised that WITH_DBUS defaults to OFF. It isn't something I particularly care about, but it seems a common enough addition and doesn't need any odd dependencies (that is, I could turn it on and build without adding anything new on my reasonably-complete system).
But what really puzzles me are the new libs since 0.91 - in my case in /usr/lib/inkscape. What is expected to use these ? I noticed them because by default they are static, although when I added -DBUILD_SHARED_LIB=ON I got (unversioned) .so libs.
For libraries only used within a package, I have no objection to static libs, it's just installing them in /usr/lib which mainly worries me (and technically does not apply here): those might accidentally get linked into something else, particularly if there is no shared lib because of some fubar in my build - and then after a vulnerability fix I would end up with old code in something - the old zlib problem.
In this case, any package using them needs to look for them in $PREFIX/$LIBDIR/inkscape, (sorry for the 'configure' naming) but are they really useful ? And if they are, should not the directory be versioned in case things change ? And finally, is it *acceptable* to you guys to make them shared, or will you tell my users that it is unsupported if they get problems with .so libs ?
Finally, it was disappointing to have to download gtest - not everybody normally runs tests (and I have no idea what the 1 test does, I couldn't find it - like I said, I don't grok cmake ;) For a prerelease it isn't a problem, but it would be nice not to have to do it for a release (i.e. let people build without running tests). Bu the script to download it was at least convenient (although perhaps users behind the Great Firewall might not appreciate it).
I very much doubt that I can produce useful "usage" comments (I keep having to google every time I build it with a new compiler / glibc / gtk / whatever and th en try to test it), but for the moment I won't be installing it until I get clarification about the purpose of the libs.
I've also got another slightly older system (gcc-6.1, gtk+-3.18) where I can test the experimental gtk3 build if that would be useful ?
But overall, this has been much less painful then when I last looked at using cmake for inkscape, so thanks for all the fixes.
1. http://www.linuxfromscratch.org/blfs/
ĸen