Rogue Wave banner
Previous fileTop of DocumentContentsIndex pageNext file
Rogue Wave Component Builder (RCB): Building Your Applications
Rogue Wave web site:  Home Page  |  Main Documentation Page

1.1 The Four Basic Build Requirements

1. SET THE INCLUDE PATH Section 1.2

The include path points to the root of the Rogue Wave buildspace that contains the components you are using. If the buildspace is located at d:\rwav, the command line specification is -Id:\rwav. Rogue Wave Standard C++ Library also requires the path -Id:\rwav\include.

2. LINK IN ROGUE WAVE LIBRARIES Section 1.3

The libraries are located in the lib subdirectory of the buildspace. That is, if the Rogue Wave buildspace is d:\rwav, the libraries are in d:\rwav\lib. If, for example, you link Essential Tools Module and trace built in the 15d configuration, your command line would include paths such as d:\rwav\lib\tls15d.lib d:\rwav\lib\trace15d.lib.

3. DEFINE THE _RWCONFIG=buildtag MACRO Section 1.4

This one command line macro defines for you all the SourcePro C++-specific command line macros required by the build, as well as a host of internal macros. For example, if you link the Essential Tools Module and trace libraries tls15d.lib and trace15d.lib, the command line macro is -D_RWCONFIG=15d.

4. SPECIFY COMPILER FLAGS AND SYSTEM LIBRARIES Section 1.5

Use the same set of compiler and linker options to build your programs that are used to build SourcePro C++ examples. The best places to find the options are in the log files and the generated makefiles. The log files show the commands executed by the makefile.

Sample Command Lines Essential Tools Module and Threads Module Trace package

Windows: where buildspace=d:\rwav and configuration=15d

UNIX: where buildspace=/usr/local/rwav, system=Solaris, and compiler=sunpro5



Previous fileTop of DocumentContentsIndex pageNext file

© 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.