This section describes how to use Microsoft Visual C++ compilers to compile programs that use Rogue Wave's Tools.h++ class library.
Before starting, be sure that the Microsoft environment variables INCLUDE and LIB are set to the proper search path for the system #include header files and the libraries, respectively.
Let's say that we have a file named myapp.cpp and that we are compiling it in a Windows NT MS-DOS command prompt. Let's also say that our Tools.h++ header files are located in c:\rwav\workspaces\WINNT4\MSVC60\4s, and that we built static version of Tools.h++ named tls4s.lib. Then we can compile myapp.cpp with the Microsoft C++ compiler with the following command (all on one line):
cl -Ic:\rwav\workspaces\WINNT4\MSVC60\4s
-D_X86_=1 -DWIN32 -DRW_NO_STL=1 -MT -GX myapp.cpp
c:\rwav\workspaces\WINNT4\MSVC60\4s\lib\tls4s.lib user32.lib
This command will compile and link in one step.
The -I option tells the compiler where to find the Rogue Wave header files.
The -DRW_NOSTL=1 option tells the header files there is no Standard C++ Library.
The -MT option creates a multithreaded executable file, using LIBCMT.LIB.
The -GX option enables synchronous exception handling.
The c:\rwav\workspaces\WINNT4\MSVC60\4s\lib\tls4s.lib path is the full path name for a no standard library, no debugging, multithreaded, static Tools.h++ library for MSVC (substitute as appropriate).
The user32.lib is the library for message-boxes and other widgets.
NOTE: Even if you are compiling a Tools.h++ Windows NT or Windows 95 console program, you still need to link in the user32.lib library, because Tools.h++ uses the Windows message box to report errors.
Microsoft Visual C++ allows you to create a Tools.h++ DLL under Windows 95 and Windows NT. Be sure to review the readme file for additional tips on using the DLL.
The dlldemo demonstration program is an example of using and linking with the DLL. It is in the <rw_root>\workspaces\<OS+ver>\<COMPILER+ver>\ <buildtype>\examples\tls<ver><osfam> directory. Additional tips on using the DLL are in the tooldll.doc readme file and in the Tools.h++ User's Guide section called "Dynamic Link Library."
To use the 32-bit DLL version of Tools.h++, you must:
Define the macros _RWTOOLSDLL and _RTLDLL on the compiler command line. This tells the Tools.h++ header files to configure for dynamic linking. If Tools.h++ is also using the Standard C++ Library, you must also define _RWSTDDLL.
Use the -MD option on the compiler command line, to use the DLL version of Microsoft's runtime library.
Link your program with the Tools.h++ import libraries. The names of the import libraries are:
Release Version (no symbolic debugging or assertions):
Tools.h++: tls4d.lib
Microsoft runtime library: user32.lib
Debug Version (with symbolic debugging and assertions):
Tools.h++: tls7d.lib
Microsoft runtime library: user32.lib
The Tools.h++ DLL is tls<build#>d.dll. Section 2.4 explains build numbers. Check the Tools.h++ Build Guide for the name of the DLL file.
When you run your program, it will search for the Tools.h++ DLL and the DLL version of Microsoft's runtime library in one of the following places and in the following order:
the current directory
the \WINDOWS directory
the \WINDOWS\SYSTEM directory
the directory containing the executable file for your program
a directory listed in the PATH environment variable
the list of directories mapped in a network
If you get exceptions, especially in *.DLLs, and you can't figure out where they're coming from, you may have incompatible *.DLLs running. Check for incompatible .DLLs in the directories indicated above.
To build a program that uses Tools.h++ under the Microsoft Visual Studio development environment, you must add the Rogue Wave include path, such as <rw_root>\workspaces\WINNT<ver>\MSVC<ver>\<buildtype>, to your studio configuration. Use the menu selection Tools | Options... to bring up the options dialog. Select the Directories tab, select Include Files from the Show Directories For: drop-down box, and add the necessary include paths.
You will also need to define any macros and compiler switches required to use a particular configuration of the Tools.h++ library.
See the Microsoft Visual Studio help system for instructions on making changes to a project configuration.
©Copyright 1999, Rogue Wave Software, Inc.
Contact Rogue Wave about documentation or support issues.