Re: [gtk-list] Re: glib portiblity

[Owen Taylor <otaylor redhat com>]

Havoc Pennington <hp@redhat.com> writes:

> SBLUNDY <SBLUNDY@CLEMSON.EDU> writes:
> > How portable is glib? I'm working on project where portiblity is a
> > concern and we are looking at glib. Linux and win32 are odvious from the
> > web page, but what about MacOS, Be, Amiga, Irix, *nix or anything else
> > out there?
> 
> Should work on anything >= 32-bit and ANSI C. Amiga/MacOS may require
> some porting work. All UNIX, Be, Win32, and MacOS X should be no
> problem.

It should be mentioned that while this is true for most of GLib, 
there are a few areas which are harder to port. The main thing
that this applies to is the main loop abstraction. If your operating
system isn't POSIX'sy enough to have select(), then you'll need
to write (more or less) a new implementation of the main loop.

Another area which may be a little hard to port is the dynamic
loading facilities in g_module.

So, if all you need is the data structures and string utility
functions, portability is easy. If you need 100% of glib, then you may
have to work a little harder.

As for existing ports, Glib should work on basically any flavor of
*nix. Full ports exist to Win32 and BeOS. A MacOS port exists
(done as part of the Mozilla project), but doesn't include the
main loop.
 
Regards,
                                        Owen