Re: [Tuxpaint-devel] fontconfig annoyance :(

[David B. <dav...@gm...>]

Hi Bill,

(my first post on Tux Paint!)

> As mentioned in the bug I posted at SourceForge, my proposed solution
> (one that doesn't involve hacking our own copies of the entire
> set of libraries all the way to the fontconfig layer:
> SDL_Pango => Pango => fontconfig) is to simply spawn a temporary
> thread at start-up, right before we go to render any kind of UI text.
>

> Guess what, though?  It doesn't work! :^(  I admit I'm new to using
> SDL's threading routines, but it turns out the issue seems to be due
> to the _forking_ (as in, "fork()" call) that we do to bring our
> OWN font loading tool to life!
>
>>
> I can't get the SDL_thread stuff to work because of our own font stuff.

Any chance you could use pthreads rather than fork() for Tux Paint's
own font-loading routine?  I probably know less about this stuff than
you do, but I recall reading somewhere that fork() and pthreads are
not compatible within the same program, and I suspect that SDL_threads
are a wrapper for pthreads.

Cheers,

David