VisualAge C++ defines a number of environment variables that you can use during the build process. You can use them in your configuration file. They are also available as predefined macros for use in your source code. The table below gives the names of predefined environment variables, and the values they have when they are defined.
| Environment Variable |
Value | When Defined |
|---|---|---|
| __IBMCPP__ | 400 | Always during VisualAge C++ builds |
| __ICC_DIR__ | The path of the configuration file in which it appears. | Aways during VisualAge C++ builds |
| __HOS_WIN__ | 1 | If the host system is Windows |
| __HOS_OS2__ | 1 | If the host system is OS/2 |
| __HOS_AIX__ | 1 | If the host system is AIX |
| __TOS_WIN__ | 1 | If the target system is Windows |
| __TOS_OS2__ | 1 | If the target system is OS/2 |
| __TOS_AIX__ | 1 | If the target system is AIX |
| __HHW_INTEL__ | 1 | If the host hardware is Intel |
| __HHW_RS6000__ | 1 | If the host hardware is RS/6000 |
| __THW_INTEL__ | 1 | If the target hardware is Intel |
| __THW_RS6000__ | 1 | If the target hardware is RS/6000 |
| __HHW_LITTLE_ENDIAN__ | 1 | If the host hardware is little-endian |
| __HHW_BIG_ENDIAN__ | 1 | If the host hardware is big-endian |
| __THW_LITTLE_ENDIAN__ | 1 | If the target hardware is little-endian |
| __THW_BIG_ENDIAN__ | 1 | If the target hardware is big-endian |
![]()
Configuration Files
How Configuration Files Are
Processed
Conditional
Processing in Builds
![]()
Configuration File Syntax
Environment Variables in Configuration
Files
