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.4 More About _RWCONFIG

The macro _RWCONFIG=buildtag works through header files generated by an RCB build. Two of these are created or modified by a build: rwconfig_product-mnemonic.h and rwc_product-mnemonic_buildtag.h. For a build of the Essential Tools Module with a build tag of 8s, these files are named rwconfig_tls.h and rwc_tls_8s.h.


The buildtag is composed of the build type tag generated by the build of the SourcePro C++ components, plus an optional user tag.

The header files are located at:

When defining _RWCONFIG=buildtag, note the build tag part of the header file name rwc_product-mnemonic_buildtag.h and append that string (excluding the leading underscore) to _RWCONFIG. In this case, the build tag part of rwc_tls_8s.h is the string 8s, which you would append to _RWCONFIG to get _RWCONFIG=8s.

If you specify one of the other build tag naming conventions when building the components, the build tag part of the header file name will be different. You must define the _RWCONFIG macro using this build tag.

Here are examples for the RCB and Verbose RCB naming conventions:

A user tag such as "baja" would affect the names as demonstrated below. Notice that dashes in header file names must be changed to underscores in the macro.



Previous fileTop of DocumentContentsNo linkNext file

Copyright © Rogue Wave Software, Inc. All Rights Reserved.

The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.