On OS/2 you can use the make message file utility, mkmsgf, during builds. This utility makes an OS/2 message file from a text file that has the correct format.
Simply supply the text files as source files for the build. If these have the file extension .mkmsgf, the build process recognizes them as message input files. If they have any other file extensions, you must explicitly specify that their type is mkmsgf. The build process runs mkmsgf automatically, as a build extension, for each message input file listed in your configuration file.
The message input file is described in the documentation of the mkmsgf command line program. The lines below show an example message input file that defines three messages.
; ;input hello.err -- English ; HLO HLO9000I:I Testing message utiltites HLO9001I:E Error message HLO9002I:W Warning message
You can apply the following option to message input files:
For example, the following lines from a configuration file make an OS/2 message file hello.msg from the textfile hello.err:
option mkmsgf_postopt("/V") {
source type( "mkmsgf" ) "hello.err"
}
The lines above have the same effect as entering the following on the command line:
mkmsgf hello.err hello.msg /V
When you make message files during a build, you can use those message files as sources in the same build. For example, you can use the make message file build extension described on this page to create a message file, and the message bind build extension to bind the messsages in the message file to an executable file. The exectuable can also be a target that you name in the same configuration file.
![]()
Configuration
Files
Build Extensions and
Specification (.ice) Files
![]()
Add or Change
Source Files
Override the Default Type of a Source
File
Bind Message Files to the Executable
Target of a Build
Compile and Bind Resources
Use Resource Sources Files as Sources
for a Build
Set Build Options
Build
![]()
Build Extensions Supplied with
VisualAge C++
The Make Message
File Utility
