4.1 Required Link Libraries

For summary tables of linking requirements for statically-linked applications, see Table 1 (Windows) and Table 2 (UNIX) below. For notes on running the resulting application, see Section 4.2, "Runtime Issues."

When building a statically-linked DB Interface Module application, you must link to a database-specific object file. The object file is in charge of notifying the RWDBManager object that the access module must be reached through a static link rather than through runtime binding.

The object files follow this naming convention:

rw<product-mnemonic><buildtag>.<extension>

where

• <product-mnemonic> is the three-letter mnemonic for the access library

• <buildtag> is the build tag assigned by RCB when the access module library was built, which depends on the naming convention you chose

• <extension> is the operating system object file extension, either .o for UNIX systems or .obj for Windows

For the Oracle access module library built in the 12s configuration, the object file would be named rwoci12s.obj on Windows and rwoci12s.o on UNIX.

Table 1 summarizes the libraries and object files you must link to on Windows using MSVC. After Table 1, Table 2 shows UNIX requirements.

The requirements for building dynamically-linked SourcePro DB applications is much simpler. You need only link to the DB Interface Module library and the Essential Tools Module library, plus any required system libraries. All other linking is done dynamically at runtime.

For notes on running the resulting application, see the next section.

Copyright © Rogue Wave Software, Inc. All Rights Reserved.

The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.