1) No. Unless one uses the "glitz" backend, which allows Cairo to render directly via OpenGL calls. However, glitz is completely undocumented and there are very few simple examples of usage anywhere (bet you can't guess I've looked into this one before!)
4) No. However, I could probably fudge a dll/so/dylib build of libsvg if need be. However, it seems libsvg is no longer supported, and now librsvg is the preferred choice of SVG support with Cairo these days. It too is LGPL, but requires some other libs (like libart) to function... making it a bit bulky.
libsvg's SVG support is ... okay... but it struggles on gradients and other things.
Licenses are annoying, eh?
I've always tried to stay away from LGPL... but if I can get the source compiling as I need it, I've occasionally gone with the "you'll need to include this dll" line, for the module (one example is the recent RTL module, where the library is LGPL).
4) No. However, I could probably fudge a dll/so/dylib build of libsvg if need be. However, it seems libsvg is no longer supported, and now librsvg is the preferred choice of SVG support with Cairo these days. It too is LGPL, but requires some other libs (like libart) to function... making it a bit bulky.
libsvg's SVG support is ... okay... but it struggles on gradients and other things.
Licenses are annoying, eh?
I've always tried to stay away from LGPL... but if I can get the source compiling as I need it, I've occasionally gone with the "you'll need to include this dll" line, for the module (one example is the recent RTL module, where the library is LGPL).