alright, bear with me for a second as i am relatively new to palm, have not
done c in a couple of years, and know little about the linking..
in my app's main module, i'm farming out a lot of the functionality to
support modules. this is nothing new. however (and maybe this isn't new
either), i'm getting a linking error that's solvable by placing macros in
the main module that define the prototypes of the support modules. this is
the only way i can find to get around undefined reference linking (basically
prototype not defined) errors generated from within the main module. it's
doesn't appear to be a very elegant solution for large apps.
so, is there a way to sequentially instruct the linker where to look? my
guess is no and i base that on the vague assumption that the main module is
linked first.. and if it's worth anything, i'm using the necessary
preprocessor directives for the .h files. so, what gives? is there another
solution?
thanks,
shawn
Shawn Hutchinson
Developer
Etensity(.com)
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
