Compiling Rogue Wave Libraries

The Problems

Theproblems to be resolved in compiling any RogueWave C++ library with KAI C++ can be summarized in just a few words: draft standard compliance. If RogueWave would release a draft standard compliant form of their libraries, then all of the known problems would go away. Rumor has it that a few months after the draft standard is approved, that RogueWave will release standard compliant forms of the libraries.

Getting Tools.h++ to Compile Today

While waiting for the draft standard, you can still use RogueWave Tools.h++. KAI has done a port of RogueWave Tools.h++ version 7.0.6 to HP-UX 10.20 using KAI C++. Since KAI C++ has a high degree of platform independence, the effort to take this port to other platforms should involve only modifications to the "rw/compiler.h" header file to reflect the target hardware.

Here is what you have to do:

• The "new" build model, using RogueWave's Software Parts Manager, is not supported. So, after purchasing Version 7.0.6 from RogueWave, and using the appropriate SPM to install the source code, you need to copy the source code to a new directory structure, rearranging it into the "old" build model. Use the script new-old.csh. The rest of these directions deal with the "old" build model directory, unless specifically stated.
• Apply patches to the toolsrc, rw, and rw/stdex subdirectories so that KAI C++ can compile them. To do this, download the file patches.tar.Z into the main directory of the "old" build model. Then execute this command: uncompress patches.tar.Z | tar xvf - to create a "patches" subdirectory. cd to this subdirectory, and run the patch.csh command.
• copy the toolsrc/makefile into the "toolsrc" subdirectory. This "makefile" is the one that was used to port RogueWave Tools.h++ to HP-UX 10.20. You will have to modify it for your site. If you build shared libraries, make special note of the changes in the commands to build shared libraries.
• copy the rw/compiler.h file into the "rw" subdirectory. This "compiler.h" file contains the settings for KAI C++ and HP hardware. If you compare it to one that you used for another compiler on the same hardware, it should be pretty easy to sort out those switch differences that are hardware dependent, and modify only those switches in this file.
• cd to the "toolsrc" subdirectory, and type make. The library will be built in the "lib" subdirectory.

Copyright © 1995-1997 by Kuck & Associates, Inc. All rights reserved.
, KAI C++ and KAI are trademarks of Kuck & Associates, Inc.