This section describes how to use Unix compilers to compile programs that use Rogue Wave's Tools.h++ class library.
To use the Tools.h++ library in your own program:
Add the directory containing the Tools.h++ header files to your include list.
Link to the appropriate Tools.h++ libraries.
For instance, to build a program called myapp you might use the following command line (all on one line):
CC -Irwav/workspaces/SOLARIS251/SUNPRO420/4s myapp.cpp rwav/workspaces/SOLARIS251/SUNPRO420/4s/lib/libtls4s.a -o myapp
The example assumes the library was exported to the rwav/workspaces/SOLARIS251/SUNPRO420/4s directory.
If you linked to a static Tools.h++ library, you are ready to run the resulting program.
If you linked to a shared Tools.h++ library, before running the resulting program, be sure that the library location is available in the environmental variable that your operating system uses to describe the possible locations of shared libraries. For many operating systems, this environmental variable is LD_LIBRARY_PATH. Some operating systems use a different name; be sure to use the one appropriate to your operating system.
This step is recommended for all shared Unix Tools.h++ libraries, and required for some platforms.
You may set the library path variable from your shell or by including it in your rc or profile script.
For example, in a Korn or Bourne shell, if your library is installed in the /rwav/workspaces/SOLARIS251/SUNPRO420/4s/lib directory, use the following command (all on one line):
export LD_LIBRARY_PATH=rwav/workspaces/SOLARIS251/SUNPRO420 /4s/lib:$LD_LIBRARY_PATH
If you are running in other than a Bourne or Korn shell, the command is:
setenv LD_LIBRARY_PATH rwav/workspaces/SOLARIS251/SUNPRO420 /4s/lib:$LD_LIBRARY_PATH
For more information on compiling using shared libraries, review the Tools.h++ readme files located in <rw_root>/parts/tls<ver>u/docs.
©Copyright 1999, Rogue Wave Software, Inc.
Contact Rogue Wave about documentation or support issues.