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.
NOTE: The buildtag is composed of the build type tag generated by the build of the SourcePro components, plus an optional user tag.
The header files are located at:
buildspace
rw
config
rwconfig_tls.h
rwc_tls_8s.h
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:
The equivalent to an 8s build in the RCB naming convention is s. The build-specific header file would be rwc_tls_s.h. Using the string s from this name, you would define _RWCONFIG as _RWCONFIG=s.The equivalent to an 8s build in the Verbose RCB naming convention is _NoThrLib_Static_Release. The build-specific header file would be rwc_tls_NoThrLib_Static_Release.h. Using the string _NoThrLib_Static_Release from this name, you would define _RWCONFIG as _RWCONFIG=__NoThrLib_Static_Release.
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.
SPM: rwc_tls_8sbaja.h ==> _RWCONFIG=8sbajaRCB: rwc_tls_baja-s.h ==> _RWCONFIG=baja_sV. RCB: rwc_tls_baja-_NoThrLib_Static_Release==> _RWCONFIG=baja__NoThrLib_Static_Release
