You can use the Information Processing Facility (IPF) to create on line documentation. The IPF compiler, ipfc on Windows and OS/2, ipf/x on AIX, takes as input a file in IPF format, an .ipf file, and creates documentation in the form of an .inf or .hlp file. You can run ipf as a build extension during a build.
To run ipf during a build, simply list the IPF files as source files for the build. If these files have the file extension .ipf, the build process recognizes them as IPF source files. If they have any other file extensions, you must explicitly specify that their type is ipf. The build process runs ipf for each IPF source file for which the resulting help file does not exist or has an earlier date than the IPF source file.
Error
messages can be found in the ipfc.log file.
You can apply the following options to IPF source files.
For example, the following lines from a configuration
file build an .inf file on OS/2:
option ipf_preopt( "/w:2" ),
ipf_output( "inf" ),
ipf_postopt( "/i" ) {
source "wpayroll.ipf"
}
The lines above have the same effect as entering the following on the command line:
ipfc /w:2 wpayroll.ipf /i
For
example, the following lines from a configuration file build an
.hlp file on Windows:
option ipf_preopt( "/q /w2" ),
ipf_output( "hlp" ){
source "wpayroll.ipf"
}
The lines above have the same effect as entering the following on the command line:
ipfc /q /w2 wpayroll.ipf
![]()
Configuration Files
Build Extensions and Specification
(.ice) Files
The IPF
Compiler
![]()
Add or Change Source
Files
Override the Default Type of a Source
Starting the IPF
Compiler
Set Build Options
Build
![]()
Build Extensions Supplied with
VisualAge C++
