On 18-May-2012 13:58, Ted Gould wrote:
What's important to realize here is that we *really* don't want to include libraries in the Inkscape codebase. It's a bad habit that we really need to kick :-) The libraries that are in the Inkscape codebase today are ones that were developed by Inkscape developers along side, or ones that we had to patch significantly.
The problem here is that I had to modify the code in libemf somewhat to get it to work. Also it isn't a very common library, so very few machines are going to have it installed.
Perhaps "library" really isn't the right term here. The 10 or so files live in one directory, but it doesn't need to build to a .a or .so or .dll, just to a .o (or .obj) which is linked into the one big inkscape library.
And that'll add all the flags and appropriate libs in.
Or not, it seems to be triggering some sort of autoconf bug/incompatibility, where it thinks there are both libemf.c and libemf.cpp, but only the latter file actually exists.
Tbanks,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech