Inkscape wants to use Bitstream Vera Sans as the default font, but I don't have that installed on my system so every character becomes ugly rectangles. I cannot figure out how to change the font to something else. I noticed that there is a Resources folder when embedding Inkscape inside a bundle, but it doesn't seem to work for the native version. Does anyone have any suggestions for putting inkscape native into an application bundle?
Looks like both were problems. I copied the definitions of IS_FINITE to 2geom/isnan.h and switched to gcc-4.0 and it compiled fine in about 4 hours. It seems to run fine, but I was having font problems. However, I recently screwed up my system fonts and I need to restart, which should fix the problems. If anyone wants it, I have terminal output of the assertion failures that happened while running.
--
Matthew Peterson
Programmer
Christa McAuliffe Space Education CenterOn Mon, Jun 16, 2008 at 6:06 PM, Michael Wybrow <michael.wybrow@...38...> wrote:
My guess would be that the isnan.h in 2geom does not have the fixes we have added to the inkscape isnan.h.
On 17/06/2008, at 3:08 AM, Matt Peterson wrote:
I have been attempting to compile a native version of Inkscape for Mac OS 10.4 on a PowerBook G4, and using the latest SVN I am getting the following error:
In file included from 2geom/sbasis.h:43,
from 2geom/concepts.h:34,
from 2geom/d2.h:39,
from libnr/nr-convert2geom.h:16,
from sp-item.h:27,
from sp-lpe-item.h:17,
from sp-shape.h:18,
from sp-ellipse.h:18,
from arc-context.cpp:27:
2geom/linear.h: In member function `bool Geom::Linear::isFinite() const':
2geom/linear.h:91: error: `__isfinite' undeclared (first use this function)
2geom/linear.h:91: error: (Each undeclared identifier is reported only once for
each function it appears in.)
make[2]: *** [arc-context.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Try copying the definitions of IS_FINITE from src/isnan.h over the ones in src/2geom/isnan.h.
Also, Matt, maybe you are using gcc 3.3? We compile our 10.4 packages with gcc-4.0, so maybe we haven't noticed a problem with gcc-3.3 on Mac OS X.
Cheers,
Michael