Home    Product Info    Orders    Downloads    About Us    Contact Us

What's New in V6.11

New Features in Make v6.11 [Top]

The following features have been added to the lastest version of Opus Make. For details of these added features and of other changes made to Make v6.11, please see the Addendum for v6.11.

• Support for Microsoft Visual SourceSafe v5.x.
• Support for Microsoft Visual C++ v5.x.
• Support of double-quoted file names as macro elements.
• For Win95, better support of mixed-case file names.
• Better support of multiple-command shell lines to ease the use of MS-DOS, Win95 and UNIX makefiles under WinNT.
• More flexible version-control-supporting .XXX_STORAGE directives.
• For Intersolv Version Manager and Burton Systems Software TLIB support, the ability to use unmangled storage-file names.
• The regular expression string substitution and "include file with regular expression matching" macro modifiers have been enhanced so that all occurrences of the matched pattern can be replaced. Previously only the first match would be replaced.
• Unknown or misspelled macro modifiers are now detected and reported.

Bugs Fixed in Make v6.11 [Top]

• Group rules would not properly link together the target groups in cases involving pathed target names and unpathed rule elements. This caused $(.TARGET,N) (N the Nth group rule element) in the group rule shell lines to evaluate to "".
• An explicit dependent with the same root name as the root name of the target is checked against the rules to see if the dependent was also the inferred source. In v6.04 and before, the rules were checked with the root name of the dependent (and full name of the target). In v6.10, this was changed to use the full path name of the dependent, breaking some makefiles. In v6.11, this has been changed to first use the full path name, then (for v6.04 behavior) to use the root name.
• Extended and Win95 versions did not work properly if "/" occurred in the PATH environment variable as can happen when using the MKS shell.
• Continued lines in UNIX versions and for NMAKE emulation were not handled right, causing problems with continued, commented lines.
• On PC platforms, UNIX makefiles terminated with \n (rather than the expected \r\n) caused read-time %foreach directives to reprocess the wrong part of the makefile.
• PC versions of Make were supposed to look for executables first in the current directory then along the PATH. However, Make prior to v6.11 did not pay attention to %chdir directives and treated the "current directory" was the same as the starting directory (MAKEDIR). Now, Make considers the directory %chdir'd into as the current directory.
• .SEARCH didn't work as documented.
• .PATHs that had a blank directory element would not be processed properly.
• Double-quoted pathnames in .PATH were not supported.
• ".OPUS_52X : TWOPASS" didn't output double-quoted target names.
• The %cd directive did not accept double-quoted directory names.
• Double-quoted file specifications for "*", "*F" and "*D" modifiers didn't work.
• On shell lines, double-quoted, whitespace-containing executable names would not be executed.
• The "A" (normalize) modifier did not properly handle UNC file names.
• The "N" macro modifier could not appear as the lower case "n".
• Win95 && WinNT "cd", "chdir" and "d:" in PolyMake/Config Builder emulation weren't "sticky".
• In a response file, Microsoft VC++ doesn't like /D on one line followed by the argument on the next line. In Make-generated automatic response files, Make now keeps /D<space><argument> together on the same line.
• "make -EP" or ".Options : MacroRecursiveDef" and a makefile macro definition that redefined a macro previously defined from the environment did not work: the macro retained its environment value.
• When Win95 Make used COMMAND.COM to execute the shell line and the shell-line redirected its output to a long filename the following problems could occur:
      - A long file names would be truncated.
      - A long directory name would result in a failed redirection.
      - Double quotes would not protect space.
• $(FOO,\=/) did not work properly in NMAKE emulation mode.
• The NMAKE-compatible {path}target syntax did not handle path in the same manner as does the newest NMAKE. Older NMAKEs required double-quotes around path elements containing spaces, but the newest NMAKE (v1.62.xxxx) doesn't.
• .OPTIONS : without any thing to the right of the colon was supposed to clear the existing options, but did not work that way.
• For Source Integrity project files, the "@<d><regex><d><subst><d>" modifier did not work.
• For Source Integrity project files, Make did not find the proper version if the source file was turned into any absolute path with the 'A' modifier.
• For WinNT Make, 4NT could not be used as an alternative shell.

New Features in MKMF v6.11 [Top]

The following features have been added to the lastest version of Opus MKMF. For details of these added features and of other changes made to MKMF v6.11, please see the Addendum for v6.11.

• Faster dependency determination. The "-s" flag now caches included files in memory. The new "-S" flag takes the place of the old "-s", specifying slow scanning with no include-file caching.

Bugs Fixed in MKMF v6.11 [Top]

• Double-quoted directory names in .HDRPATH were not accepted.
• Double-quoted file names were not output.
• Would not handle includes where the include statement used double-quoted file names where the file name used double backslash as the directory separator and the file name was an absolute path. That is, something like this didn't work: #include "\\vc40\\include\\windows.h"
• Would not output %include directives if hidden by a false conditional in the makefile.
• The -cs might not output all dependencies of recursively included header files, but the conditions where MKMF failed were obscure.

Home    Product Info    Orders    Downloads    About Us    Contact Us

Opus Software, Inc. 1032 Irving Street, Suite 439 San Francisco, CA 94122 USA
Phone: 415-485-9703 Fax: 415-485-9704 Email:biz@opussoftware.com