[Hit the old "send" button a little too early last time; mea culpa]
I am trying to build a shared library using the latest prc-tools.
When I get to the link phase:
m68k-palmos-gcc -palmos3.5 -shared -g -o AAMMexample1 ../aamlib.o
AAMMexample1.o
I get the following error:
/usr/local/m68k-palmos/bin/ld: cannot open -lscrt: No such file or directory
collect2: ld returned 1 exit status
Indeed there is no libscrt.a in /usr/local/m68k-palmos/lib
I'd appreciate any advice; I seem to be doing everything the way that
others are.
While we're at it, a secondary question:
I want to give plug-in developers a .o that is the shared library setup
with dispatch table, etc., and a .h, and allow them to build plug-ins that
link to the .o and are required to have an init routine of a particular
name (said name to be compiled into the .o I give them). Then I can
dynamically load and unload code modules as shared libraries.
The problem I see potentially is that every one of these plug-ins will have
the same creator, type, and name. What is a good approach that will allow
me to enumerate the libraries in my master program and differentiate them?
Thanks again,
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/
