>When used in conjunction with prc-tools, the term "shared library" is
>ambiguous; there are two kinds: system and GLib.
Sorry, my fault. I am trying to build a GLib this time; I like my globals
and statics, but don't yet have the experience needed to muck seriously
with extralogues and a4 and a5. Right now I'm just trying to get something
up and running. I'm considering building my GLib using Sokolov's (sp?)
prc-tools 0.6.0, then building my main app using your prc-tools 2.0.90 so I
get the A5 advantages in the latter. I'd appreciate any comments on that as
a temporary approach, be they good or scathing.
>Last time (April 6th) you said you were trying to build a *system* shared
>library, so I'll assume that's still the case.
Mea culpa. Sometimes when you're in a tiny startup a month can seem like a
year. ;-)
>I wrote an example system shared library for use with prc-tools 2.0.91.
>It works for me (prc-tools 2.0.91, Red Hat 6.2). It would be helpful if
>you would download it and attempt to build it.
I'll do this anyway just for the practice and to verify for you that a mere
mortal can build it. I'll go get 2.0.91 now.
Do you know of a good reference for some of the things that are lightly
touched upon in the prc-tools docs regarding a4, a5, globals access,
prologues, epilogues, swapping in code resources without using a library at
all, that sort of thing? I think we're going to have to employ multiple
mechanisms to do what we want to do (just using naked shared libs of either
flavor isn't going to cut it), but I also know that we have no need to
reinvent the wheel because anything we'd want to do has been done to death
already. I just need to educate myself further on those tricks of the trade.
Thanks again, John.
Curtis Jackson
Director of Engineering
Aniwhere, Inc.
[EMAIL PROTECTED]
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
