This section discusses the software requirements.

There are four SourcePro C++ products: SourcePro Core, SourcePro DB, SourcePro Net, and SourcePro Analysis. The modules of these products incorporate the functionality of many previous Rogue Wave products.

For additional information on compatibility, please consult the SourcePro C++ Release Notes. A PDF version of the release notes is in the top-level directory of the SourcePro C++ installation and also available on the Rogue Wave website at http://www.roguewave.com/support/product-documentation/sourcepro.aspx.

Rogue Wave tests the modules in each version for compatibility with one another. Rogue Wave does not test the compatibility of modules in a current version against a previous version. Web-only downloads between releases are generally compatible with the most recent release, but this is not guaranteed.

For information on building components and applications, please see the manuals Installing and Building Your SourcePro C++ Products and Rogue Wave Component Builder (RCB): Building Your Applications.

SourcePro C++ continues to enhance and extend the APIs it provides. In some cases, new APIs have been introduced that supersede previous APIs. These new APIs often provide cleaner interfaces, improved performance, or improved safety compared to the older functions. In these scenarios, the older functions have been deprecated, and are no longer recommended by Rogue Wave.

Deprecated APIs are listed on a page of the SourcePro C++ API Reference Guide. Deprecated classes and members are still documented, but are clearly marked as deprecated at the beginning of their descriptions. The deprecation warning indicates the release in which the API became deprecated and suggests the new API to use.

To help you detect the use of deprecated APIs in your code, Rogue Wave provides a compilation macro RW_DISABLE_DEPRECATED. When RW_DISABLE_DEPRECATED is defined, all deprecated -SourcePro APIs are removed, causing compilation failures in any code that relies on them. You can use the information gained from these failures together with the guidance in the Class Reference documentation to update your code to rely on improved APIs.

In addition to the publicly documented SourcePro APIs, you may discover undocumented APIs. These APIs are not supported for use in end-user code, and are subject to change or removal without warning in future releases.

The phrase “the X Module depends on the Y Module” means that the Y Module must be built before the X Module. The Rogue Wave Component Builder (RCB) checks that dependencies are selected and installed, and ensures that they are built in the proper order. If you are installing prebuilt libraries, the dependencies are already satisfied and included in the set of prebuilt libraries.

All Rogue Wave SourcePro C++ modules depend on the C++ Standard Library and the Essential Tools Module. Beginning with Edition 11 of SourcePro C++, all modules are built using the native C++ Standard Library that comes with your compiler. The only exception to this is on Sun Solaris platforms, where you have the option of using STLPort.

In addition to dependency on the Essential Tools Module and the C++ Standard Library, individual modules may have other dependencies. These module-level dependencies are summarized in Table 1. Package-level dependencies are explained in the user’s guides of individual modules for the convenience of developers who prefer to specify builds by individual packages.

SourcePro C++ uses open source or freely licensed code, and commercially licensed code, as detailed in the following sections. The text of the license agreements can be found in Appendix A. These licenses are also included in the product distribution, as identified in the file 3rd-party-licenses.txt in the installation 3rdparty directory. This file also identifies the exact version number currently installed in SourcePro C++

Table 2 identifies the open source or freely licensed code shipped with SourcePro.