Changes between Version 7 and Version 8 of WPIBuild
- Timestamp:
- Oct 6, 2008, 1:16:11 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WPIBuild
v7 v8 8 8 * A functional FM/2 build environment. ([/repos/fm2/trunk/BUILDING See build instructions] elsewhere for details.) 9 9 * Open Watcom v1.6 or later 10 * OS/2 Develo eprs Toolkit v4.5 or newer10 * OS/2 Developers Toolkit v4.5 or newer 11 11 * SVN 12 12 * A local copy of the SVN repository of FM/2 source files 13 13 * WarpIN, version 0.9.20 or later, installed 14 * OS/2 (or eCS) with REXX support 14 15 * A functional version of SED installed 15 16 … … 22 23 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. 23 24 FM2UTILS_VER:: 24 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. (NOTE: FM2UTILS rarely changes so this variable will rarely need to be changed.)25 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. (NOTE: FM2UTILS rarely changes so this variable will rarely need to be set.) 25 26 26 27 === How to build the WarpIN installation files of FM/2 === … … 31 32 b. Obtain a copy of FM2UTILS.ZIP and unzip it into this '''FM2Utils''' directory. 32 33 4. (Optional) Make any desired changes to local copies of the files within the build subtree. 33 5. Build the WarpIN installation files of FM/2 using ''' NMAKE DIST''' or '''NMAKE WPI'''.34 * ''' NMAKE DIST'''35 * ensures that the rest of FM/2 is built and should be used every time the local copy of any FM/2 source files have been changed. 36 * performs LXLITE compression of the executables. 37 * builds the WPI file(s) 38 * ''' NMAKE WPI'''39 * only builds the WPI files so it is faster than ''' NMAKE DIST'''.40 * will not work correctly unless ''' NMAKE DIST''' has been at least once beforehand.41 * is intended to be used by those who aremaking modifications to the WarpIN installation files for FM/2 (See below.). As these programmers develop and test their changes they will be repeatedly building WPI files when the only changes that have been made is to the WarpIN-related files or environment variables:34 5. Build the WarpIN installation files of FM/2 using '''WMAKE DIST''' or '''WMAKE WPI'''. 35 * '''WMAKE DIST''' 36 * ensures that the rest of FM/2 is built and should be used every time the local copy of any FM/2 source files have been changed. WMAKE ALL does just this step. 37 * performs LXLITE compression of the executables. WMAKE LXLITE does just this step. 38 * builds the WPI file(s). WMAKE WPI does just this step. (See below.) 39 * '''WMAKE WPI''' 40 * only builds the WPI files so it is faster than '''WMAKE DIST'''. 41 * will not work correctly unless '''WMAKE DIST''' has been run at least once beforehand. 42 * can be used instead of WMAKE DIST by those who are only making modifications to the WarpIN installation files for FM/2 (See below.). As these programmers develop and test their changes they will be repeatedly building WPI files when the only changes that have been made is to the WarpIN-related files or environment variables: 42 43 * warpin\fm2.wis.in (the WarpIN script) 43 44 * warpin\bld_fm2_wpidirs.txt