Cross compiling swt and gtk: CVS head or not?

Thursday, October 25th, 2007 | Free Software

Finally. After too many hours on such a ’simple’ thing, I’ve managed to get swt up and running on a (rather) small device (with a PPC) with gtk as backend. What did I do wrong? For some reason I didn’t get the Freetype support into pango.
So when compiling the following code:

PangoFontMap *
pango_cairo_font_map_new (void)
{
/* Make sure that the type system is initialized */
g_type_init ();

#if defined(HAVE_CAIRO_ATSUI)
return g_object_new (PANGO_TYPE_CAIRO_ATSUI_FONT_MAP, NULL);
#elif defined(HAVE_CAIRO_WIN32)
return g_object_new (PANGO_TYPE_CAIRO_WIN32_FONT_MAP, NULL);
#elif defined(HAVE_CAIRO_FREETYPE)
return g_object_new (PANGO_TYPE_CAIRO_FC_FONT_MAP, NULL);
#endif
}

the pre processor passed on to the #endif statement and, yup, crap will be returned when executing. When the function returned 0xd (13 in decimal) I was quite sure something was wrong.

OK, I was just about to write a bug report to pango when quickly checking the latest version of the function. It’s now fixed. The function returns 0 after the last #endif .Perfect.
But this leads to the non-answerable question:

Should one go for CVS head or the latest stable release???

1 Comment to Cross compiling swt and gtk: CVS head or not?

Björn
October 28, 2007

Personally, I’d go with the stable. I’ve been running FreeBSD for quite a while, and for the two years I ran CURRENT, I saw a lot of funky stuff that definitely didn’t show up in STABLE. My guess is, that will happen in most OSS/FOSS projects.

Leave a comment

You must be logged in to post a comment.

Search