Plus don't forget a shared library has no access to globals, which included (IFAIK) static member variables of a C++ class.
Alan <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Hi > > > > I'm looking into porting a large C++ library to the PalmOS (v3.5 and > > higher). The library is certain to become bigger than 64K. Exceptions > and > > 1) create a GLib shared library. > > > > 2) create a mulit-segment application. > > > Your app will be multi-segment, but that's not a > big issue since the compilers doing all the work. > You've just got to learn a small set of things > about managing muti-segment sets of source. > > As far as the library goes the approach I used was > to break the library up into logical modules and > implement each module as a static library. You > don't specify whether you need this library to be > shared or not, but then the same thing is true - > split it into managable modules. > > I understand that there are ways to build multi- > -segment shared libraries, but I would have > thought that things like debugging would become > more difficult. > > Chris > Tutty > > ------------------------------------------------ > This message was sent using InSPire Net Webmail. > http://www.inspire.net.nz > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
