You should also use Software Parts Manager to build the examples for the Rogue Wave libraries you build. Examples built through Software Parts Manager essentially give you insight to Rogue Wave developers' unique knowledge of how best to build applications using a particular library. You can then use the build transcripts and makefiles generated by these builds to guide you in determining the requirements for your application build.
If your application uses a Rogue Wave library that depends on other Rogue Wave libraries, it makes sense to use the transcript and makefile from the build of this library's examples as a resource. Because of the consistency requirement, the build configuration for these examples must not only meet the requirements for the library, but also those for any libraries on which the library depends. For example, the build configuration for the DBTools.h++ examples obviously must meet the requirements for DBTools.h++ itself and the access library you are using, but also for Tools.h++ on which DBTools.h++ depends, and possibly for the Standard C++ Library if Tools.h++ was built on top of that.
©Copyright 1999, Rogue Wave Software, Inc.
Contact Rogue Wave about documentation or support issues.