Re: Porting GTK, requirements

["Joost Faassen" <listreader joost cx>]

The relevant pieces of the picture are:

> - The operating system environment ... libraries etc.
>   Porting GLib deals with differences here.
The os env is not posix compliant at all, however a lot of basic
functionality is in place such as memory management, filesystems, etc. Is
there a central place where for example stubs need to be filled to hook
into this ?

How dependant on scheduling / tasks etc is GTK ? Could it run in a
monotasking system for example ? Does GTK create any tasks / processes on
its own ? Does it require some form of IPC ?

> - The font system in use (X11, FreeType, Win32, etc.)... This
>  involves Pango.
Hmm this might be a seperate issue, just some very simple bitmapped font
rendering is in place, should I panic ?

> - The windowing system in use (X11, Win32, framebuffer, etc.)
> There are two sets of framebuffer code ... the linux-fb code in in the
> GTK+ distribution and the directfb port of GTK+ (http://www.directfb.org)
> Both are linux specific; the linux-fb code is probably easier to port to
> a different keyboard/pointer/framebuffer API because it is much simpler
> and more self contained.
Following Sven's comment, I'll have a look at the directfb.



Thanks!
Joost Faassen