I asked the Poppler guys if they could define macros with their version info in them, so that the version could be sensed at compile time. I don't know what they want to do.
The problem is that the Inkscape code calls internal Poppler, stuff and not their public API. So there are no promises that there will not be more breakages in the future. The Poppler guys know that we are using their code improperly. But they also -like- us using Poppler in Inkscape (they helped with the fix). So in the future there might possibly be a more stable low-level way of catching parsing events. Maybe registering a callback?
bob
Valerie wrote:
Thank you! Thanks to you all I've solved the problem! :D
And yes, the problem was with the Poppler update.
I've managed to find the same problem with 0.46 through Google, as well as a corresponding fix.
So for CVS, you just need to find back the right lines:
Line 2344:
- Unicode u[8];
- Unicode *u = NULL;
Line 2392:
u, (int)(sizeof(u) / sizeof(Unicode)),&uLen,
&u,&uLen,Line 2441:
u, (int)(sizeof(u) / sizeof(Unicode)),&uLen,
&u,&uLen,Inkscape compiles after that.
./configure CFLAGS="-DPOPPLER_NEW_GFXFONT"
I guess that would work too. XD
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel