On OS/2 you can use the message segment binder utility, msgbind, during builds. This utility binds a message segment to an executable program.
All you need to do is supply msgbind input files as sources for the build. If these input files have the file extension .msgbind, the build process recognizes them as msgbind input files. If they have any other file extensions, you must explicitly specify that their type is msgbind. The build process runs msgbind automatically, as a build extension, once for each msgbind input file listed in your configuration file.
The msgbind input file is a text file that identifies the executable files, output message files, and message numbers to be bound. It is described in the documentation of the msgbind commnd line program. The lines below show an example msgbind input file to bind a message file named hello.msg to an executable file named hello.exe:
;input file for msgbind >hello.exe <hello.msg *
For example, if the file above is named infile, the following line from a configuration file runs msgbind with infile as the msgbind input file:
source type( "msgbind" ) "infile"
The line above has the same effect as entering the following on the command line :
msgbind infile
When you run msgbind as a build extension, you can bind to an executable file that is a target in the same configuration file. You can also create the message files during the build, by using the mkmsgf build extension.
![]()
Configuration
Files
Build Extensions and
Specification (.ice) Files
![]()
Add or Change
Source Files
Override the Default Type of a Source
File
Make Message Files During 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 Message
Segment Binder Utility
