3.6 Module-Specific Questions

Section 3.5 explained the general questions which you must always answer when creating a buildspec.

This section explains questions that appear only when specific modules are included in a buildspec. In addition, some questions in this section are displayed only if advanced questions are set to be available.

These modules generate additional build option questions:

The Essential Tools Module requires the selection of an RWCString (and associated RWWString) implementation. In addition, two macros may be set governing whether to enforce the use of four-digit years and to override the default RWZone class settings with system settings.

The Essential Tools Module provides two implementations of RWCString and RWWString: RWStandardCString based on std::string and RWCopyOnWriteCString built using the Copy-on-Write idiom. Your selection should be governed by the requirements of your applications, as described here.

The default is to use RWStandardCString (with RWStandardWString). RWCString and RWWString respectively become aliases for the selected classes.

For more information, see Section 4.11, “Performance Considerations,” in the Essential Tools Module User’s Guide.

This macro question is visible only when the Show advanced questions box is selected on the Options dialog’s Advanced Questions tab.

Enabling the RW_CENTURY_REQD macro causes a debug assertion in debug mode or an exception in release mode if a non-four-digit year is entered. This is useful mainly for debugging. The default setting is no.

The Internationalization Module is dependent on the IBM International Components for Unicode (ICU). RCB asks two questions regarding your copy of the ICU.

When installing the Internationalization Module, you must select whether you want to use an ICU installation provided by Rogue Wave or an ICU that is already installed on your machine.

If you select Use the ICU supplied by Rogue Wave, RCB automatically finds the path to the ICU installation. If you choose Use my own installation of the ICU, you must specify the path. The default value is Use the ICU supplied by Rogue Wave.

If you chose Use my own installation of the ICU, you must specify the path to the ICU installation.

When specifying the absolute path, be sure to provide the path up to, but not including, the lib and include directories. For example, use C:\icu instead of C:\icu\lib or C:\icu\include.

All questions related to the Threads Modules are advanced questions. They are visible only when the Show advanced questions box is selected on the Options dialog’s Advanced Questions tab.

This option sets the level of trace information produced from trace-enabled packages or trace-enabled user code.

The setting for trace-enabled packages dictates what level of trace information is produced from SourcePro C++ packages and modules that support tracing.

The setting for trace-enabled user code dictates what level of trace information is preserved for your own code.

The default setting, Disabled, preserves no tracing output, and results in all references to the tracing package being compiled out of code. This results in smaller, faster executables at the cost of execution tracing information.

For all other trace levels, tracing code is compiled in, resulting in larger and potentially slower executables. Selecting the Entry/Exit trace level results in trace event generation for every traceable function, which can have a negative effect on application performance. For more information about the tracing mechanism, refer to the Threads Module User’s Guide.

If you are using a Windows-based operating system, you must select whether or not you want to implement an RWMutexLock based on CRITICAL_SECTION.

Applications that use this implementation can significantly increase their performance speed. However, implementing this feature will make those applications undeployable on some platforms and unable to use certain methods.

When installing the Secure Communication Module, you must select your cryptography library. Rogue Wave ships with a pre-built version of OpenSSL, or you can choose to use your own installation.

If you select the OpenSSL installation supplied by Rogue Wave, you do not need to specify its location. If you select to use your own installation of OpenSSL, the Library Location screen launches.

The Library Location screen requires you to enter the path to your cryptography library.

When specifying the location of the cryptography library, be sure to provide the path up to, but not including, the lib and include directories.

For example, on a Windows platform, use D:\openssl instead of D:\openssl\include or D:\openssl\lib. On a UNIX platform, use /usr/local/openssl instead of /usr/local/openssl/lib or /usr/local/openssl/include.

If your OS is Windows-based and your installation directory contains spaces, you must surround the directory with quotes to allow the Visual C++ compiler to properly parse the compile and link commands.

Windows provides a mechanism for replacing long directory names with their DOS 8.3 equivalent names. The command DIR /X displays a directory listing that includes the DOS 8.3 names for long directory names or directories that contain spaces. For the example above, the DOS 8.3-compatible directory is:

RCB allows you to choose between seven different database access modules: DB2 CLI, Microsoft SQL Server, MySQL, ODBC, Oracle OCI, PostgreSQL, and Sybase. When installing any of these access modules, as well as its examples, you must specify a number of fields to allow your examples to connect to a relational database server with a valid user name and password.

While each of the DB Access Modules prompts have minor differences, they follow the same pattern as the screen below.

To connect your examples to the database, you must provide all required connection information. The table below lists all the potential fields that may be used when installing a DB Access Module.

Specify the version of the database to be used. Some databases have multiple supported versions. Others have only one supported version.

Specify other options, such as the packet-size for the Sybase client. If no options are specified, leave this field blank.

If you have any questions about the required options, see the access module user’s guide, located at buildspace\docs\html\<access-lib-mnemonic>ug. For example, the Oracle OCI user guide is located at buildspace\docs\html\oracleociug.

You can also access any of the documentation from the general index at buildspace\docs\html\index.html.

Information on environment variable settings for the various database clients can be found in the Building Your Applications.

For MS SQL Access Module, there is an extra option, SQL Server Client, which can have following values:

1. SQL Server – For building SourcePro applications with the MS SQL Server driver provided by MDAC.

2. ODBC Driver for SQL Server – For building applications with ODBC Driver for SQL Server. The ODBC Driver for SQL Server SDK is required for this option, generally installed at the following location:

3. SQL Server Native Client – For building applications with SQL Server Native Client Driver shipped with Microsoft SQL Server. SQL Server Native Client SDK is required for this option, generally installed at the following location:

If the last two options are selected, the path to the SDK needs to be entered on the following screen.

If the build of the examples failed because of incorrect information entered for the database connection parameters, you must delete the examples directory where the failed build results were placed before you rebuild the examples. For example, if you attempted to build examples for ODBC in the 8s configuration and the build failed, you must first delete buildspace\examples\odbc\8s before you can rebuild the examples.

If you do not delete the directory, RCB fails to re-parse the connection information and continues to use the erroneous information, resulting in another failed build.

Alternatively, to rebuild the examples, do the following. Go to the build directory (for example, buildspace\examples\odbc\8s), edit the file tutdefs.h and update the values. Execute the make clean (or nmake clean) command, and then execute the make (or nmake) command.

Support for the DB XA Module is available only when Rogue Wave Professional Services installs and configures the DB XA Module for specific platforms and XA-compliant Transaction Processing Monitors (TPMs). Please contact your Rogue Wave account representative for more information.

When building the Essential Math Module, you must indicate the type of Basic Linear Algebra Library to be used.

Select which Basic Linear Algebra (BLA) library to use, which is required by the Math Module.

The Intel Math Kernel Library (MKL) and the Sun Performance Library (SPL) are performance-enhanced libraries for their respective platforms. On AIX and HPUX, this screen does not display and Netlib CLAPACK is automatically selected because Rogue Wave has not certified these platforms for any performance-enhanced libraries with the Math Module.

If you select the MKL or CLAPACK, you must specify whether you want to use a previously installed version or the version provided by Rogue Wave, which is the default:

For MKL and CLAPACK, if you selected “Use my own installation of the MKL” or “Use my own installation of CLAPACK” in the selection window, specify the location of the previously installed version.

When entering the absolute path to the library, be sure to enter the path up to the subdirectory where it is stored. For example, C:\Program Files (x86)\Intel\Composer XE\mkl\lib\ia32\lib for the MKL or C:\clapack\windows\ia32-msvc-9.0\lib for CLAPACK.