Building WarpIN (WPI) install files for FM/2

Prerequisites

• A drive with long filename support
• A functional FM/2 build environment. (See build instructions elsewhere for details.)
  • IBM VisualAge C++ version 3.65 with FP2 (Soon to be Open Watcom.)
  • OS/2 Develoeprs Toolkit v4.5 or newer
  • SVN
• WarpIN, version 0.9.20 or later, installed
• A functional version of SED installed

How-to

1. Use SVN CHECKOUT and/or SVN UPDATE to ensure you have the latest source files.
2. From the base of the source subtree, use NMAKE ALL to ensure you have the latest binaries.
3. (Optional) Set environment variables to manage/customize the Warpin file creation. (See below for details.)
4. From the base of the source subtree, use NMAKE DIST which will compress the executables and build the WarpIN installation files.

NOTE: If repeated builds of WarpIN installation files from the same FM/2 binary files are needed/desired, then repeated compression of the executables is not needed. Use NMAKE WPI to skip the compression steps and just build the WarpIN files.

Customizing the WPI build through environment variables.

BUILD_FM2UTILS

By default, a WPI file is cretaed for both FM/2 and the optional, separate FM/2 utilities package. To prevent the creation/update of the FM/2 Utilities WPI file, use SET BUILD_FM2UTILS=0.

FM2_VER

The WPI file for FM/2 is named FM2<version-string>.WPI. The <version-string> portion of the file name can be set through the FM2_VER environment variable. For example, SET FM2_VER=-3-5-9 will result in FM2-3-5-9.WPI being created/updated.

FM2UTILS_VER

The WPI file for FM/2 Utilities is named FM2UTILS<version-string>.WPI. The <version-string> portion of the file name can be set through the FM2UTILS_VER environment variable. For example, SET FM2UTILS_VER=-1-0-1 will result in FM2UTILS-1-0-1.WPI being created/updated.