When you build a series of dependent libraries, they must be built consistently, using the same command line macros and flags. Furthermore, in most cases these same macros and flags (or related ones) will be required for building applications that depend on these libraries. The lesson here is: plan ahead. Think about the functionality you require in your application, and be sure to build the libraries with the correct macros and flags to support that functionality.
Fortunately, Software Parts Manager is designed to encourage consistency in builds. By selecting one of Rogue Wave's standard build configurations and using it to build your suite of libraries, consistency is assured. You can also create a custom build configuration, based on one of the standard configurations but specifying special compile and link options you may require for your application.
By specifying the compile and link options in the custom configuration, the build of the examples serves as a testing ground for your application build. Also, the makefile and transcript from the examples build can provide insights into the command line requirements for building your application.
The procedure for creating custom build configurations is in Section 2.4.1, "Creating a Custom Build Configuration."
©Copyright 1999, Rogue Wave Software, Inc.
Contact Rogue Wave about documentation or support issues.