Chris: I used a naming convention for my libary routines to avoid the
collision with the "native" application code routines. Typically, an
application routine called "UpdateDBField" would do some context sensitive
setup processing then call "xxUpdateDBField" where all the hard work is
done. (where "xx" is an arbitrary prefix for my library routine).
Then, I created a new project called "appnameDebug" by cloning the existing
"native" application project, then added the complete library source to the
application's project. Then, enabled Debug on all source members, and could
then step into and out of application and library routines.
Of course, you have to keep separate 3 separate projects: one for the
"native" application, one for the "native" library, and one for the complete
"debug" version. A small price to pay for the ability to debug those
routines at the source level.
> Do I need to add the library project source to the main project? I tried
this and this causes all sorts of problems, like
> for instance if I have a library project source file with the same name as
a source file in the main project it doesn't let me add it, meaning I can't
build and debug. Doing this would also cause lots of version control
headaches, and kind of defeats the exersise of building a library in a
separate project in the first place. There has to be an easier way?
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
