Margus Freudenthal <[EMAIL PROTECTED]> wrote:
> I would like to develop a shared library that will be distributed
> primarily in binary form. Which shared lib format should I use: GLib or
> SysLib?
This depends *solely* on the purpose of your library and nothing else. If it is
a system extension that deals more with the OS than the currently running app,
must keep its open state when one app exits and another starts, etc., like for
example the Net Library, make it a SysLib, as that's what they are for. If it
is application-level code that could just as well be a static library, please
do yourself and the PalmOS community a favor and don't use the system extension
mechanism for frivolous application purposes. Instead, use something that is
designed for application-level shared libraries. This means using GLibs or
inventing something of your own. I go with GLibs in such cases.
> SysLib is supported by both CW and GCC [...]
The prc-tools-0.6.0beta distribution on ftp.jpsystems.com includes a utility
that runs under UNIX with the other GNU tools but generates GLib caller stubs
that the Metrowerks compiler can swallow. You distribute the files it generates
to your CodeWarrior users and they will be able to call your GLib. You can call
GLibs from CodeWarrior, although you can still create them only with PalmOS gcc
(or by typing up the PRC in a hex editor).
--
Michael Sokolov 2695 VILLA CREEK DR STE 240
Software Engineer DALLAS TX 75234-7329 USA
JP Systems, Inc. Phone: +1-972-484-5432 x247
or +1-888-665-2460 x247
E-mail: [EMAIL PROTECTED] Fax: +1-972-484-4154
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
