Rogue Wave web site: Home Page | Main Documentation Page
6.3 Required Link Libraries
To build an application that uses the Secure Sockets Package of the Secure Communication Module, you must link to:
The Essential Tools Module library
The following package libraries from the Threads Module: Smart Pointer (pointer), Synchronization (sync), Thread-compatible Exceptions (threxcept), and Execution Tracing (trace)
The Secure Communication Module (secsock) package library, and the Essential Networking Module (network) package library.
The underlying cryptographic library (RSA BSafe or OpenSSL)
System libraries
For specific information about linking to these libraries for static and dynamic builds, see the next two sections.
6.3.1 Linking to Cryptographic Libraries for Static Applications
When building a static Secure Sockets Package application, you must link to the static version of the underlying cryptographic package.
If you are using OpenSSL, link to libeay32.lib and ssleay32.lib on Windows, libcrypto.a and libssl.a on UNIX.
If you are using RSA BSafe, link to sslc.lib and rcom.lib on Windows, libsslc.a and librcom.a on UNIX.
6.3.2 Linking to Cryptographic Libraries for Dynamic Applications
When building a dynamically-linked Secure Sockets Package application, the linking requirements differ significantly depending on the cryptographic library you are using.
6.3.2.1 Dynamic Applications Using OpenSSL
OpenSSL can be built as a dynamic library, so you link to both the SourcePro C++ and OpenSSL dynamic libraries.
On Windows, the libraries you link to are named the same as the static versions, libeay32.lib and ssleay32.lib. However, the dynamic libraries are much smaller than their static equivalents because they simply point to the main OpenSSL DLL library that contains the actual code. Be careful to point to the dynamic versions of these libraries.
On UNIX platforms, the names of the dynamic libraries are libcrypto.so and libssl.so (or whatever extension your platform uses for shared objects).
6.3.2.2 Dynamic Applications Using RSA BSafe
RSA does not provide dynamically linked versions of their libraries. If you specified the RSA library when you built the SourcePro C++ secsock library, the build pulled all the required functions from RSA's static library into the SourcePro C++ dynamic library. Therefore it is only necessary to link to the SourcePro C++ Secure Sockets Package library (secsock).
© Copyright Rogue Wave Software, Inc. All Rights Reserved.
Rogue Wave and SourcePro are registered trademarks of Rogue Wave Software, Inc. in the United States and other countries. All other trademarks are the property of their respective owners.
Contact Rogue Wave about documentation or support issues.