home | build-o-rama | programming links | mailing list | search

Visual C++
command-line
compiling


When running Visual C++ 1.0 or 1.5 under OS/2, you can't do builds directly from the IDE as under normal Windows; you can do them with NMAKE in a DOS box (using the makefile generated by the IDE).

The DOS box must have settings of:

You will also need to run MSVCVARS.BAT to set up the environment. This file is usually created in the C:\MSVC\BIN directory. This can best be done from a custom AUTOEXEC.BAT file for the DOS box.

Other compatibility issues

The following is based on my experiences, and may not be comprehensive.

MSVC must be run in Enhanced mode for WinOS/2. Aside from the compiling features, all the rest of the features of the Windows IDE appear to work fine, including the built-in debugger. The CodeView debugger probably will not work.

Users of Visual C 1.0 may need to obtain the OS2FIX.ZIP patch, which is available for download from this site or from the MSLANG forum on CompuServe. This patch does not allow builds from the IDE; it simply fixes the Phar Lap DOS extender so it works with OS/2 for command-line builds.

Microsoft Visual C++ 2.0 and later are 32-bit-only compilers, which run only on Win32 systems such as Windows NT and Windows 95.

Three Cat Software home page