home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Professional
/
OS2PRO194.ISO
/
os2
/
patches
/
ms-c7
/
readme.os2
< prev
next >
Wrap
Text File
|
1992-05-08
|
12KB
|
299 lines
README.OS2 File
Release Notes for Microsoft(R) C/C++, Version 7.0
OS/2 Hosted Add-on Kit
(C) Copyright Microsoft Corporation, 1992
This document contains release notes for the OS/2 Hosted Add-on Kit
for Microsoft C/C++ version 7.0.
===============================< CONTENTS >================================
This document has the following sections:
Part 1: Product Description
Part 2: Setup Information
Part 3: Product Notes
======================< Part 1: Product Description >======================
Terms
-----
Throughout this document, the term "C7 for OS/2" refers to the OS/2
Hosted Add-on Kit. The components of C7 for OS/2 are listed below
under "Product Components."
The term "C7 for MS-DOS and Windows" refers to the Microsoft C/C++
version 7.0 package for MS-DOS(R) and Microsoft Windows(TM), including
the Microsoft Windows Software Development Kit (SDK).
Introduction
------------
C7 for OS/2 runs with OS/2 version 1.x. It will create applications
targeted for the MS-DOS and Microsoft Windows operating systems only.
It will not create applications that run with the OS/2 operating system.
C7 for OS/2 is an add-on package to C7 for MS-DOS and Windows. C7 for
MS-DOS and Windows must be installed before C7 for OS/2 can be used to
create applications.
System Requirements
-------------------
The hardware requirements for C7 for OS/2 are the same as the hardware
requirements for C7 for MS-DOS and Windows (listed on page 18 of the
Microsoft C/C++ Getting Started book).
The OS/2 operating system, version 1.1 or later, is required.
Package Contents
----------------
Check your C7 for OS/2 package to see if everything is there. If any
pieces are missing or if you have problems with the disks, contact
Microsoft Customer Service (1-800-426-9400). In the package, you
should find the following items:
- Two disks. The files contained on these disks are listed in the
PACKING.OS2 file on disk 1.
- This document (also available on disk 1 in the README.OS2 file).
- The C7 for OS/2 License Agreement.
Product Components
------------------
C7 for OS/2 contains the following components:
- OS/2 hosted C/C++ compiler
The OS/2 hosted compilers have the same names as their MS-DOS
hosted counterparts, with the following exceptions:
MS-DOS hosted OS/2 hosted Compiler
------------- ----------- --------
C13216.EXE C11616.EXE pass 1 compiler
C1XX3216.EXE C1XX1616.EXE C++ pass 1 compiler
C23216.EXE C21616.EXE pass 2 compiler
C33216.EXE C31616.EXE pass 3 compiler
- OS/2 hosted utilities
The utilities provided with C7 for OS/2 have the same usage and
function as their counterparts in C7 for MS-DOS and Windows. The C7
for OS/2 utilities installed in the BINP subdirectory can be run
only with OS/2. The utilities in the BINB subdirectory are bound
executable files that can be run with MS-DOS or OS/2.
- OS/2 hosted Programmer's WorkBench (PWB)
The OS/2 hosted version of PWB is the same as the MS-DOS hosted
version included with C7 for MS-DOS and Windows, with a few
exceptions that are described in Part 3 below.
- This C7 for OS/2 Release Notes file.
=====================< Part 2: Setup Information >=========================
You must install C7 for MS-DOS and Windows before you can use C7 for
OS/2. The C7 for OS/2 setup program does not create libraries or
header files. The C7 for MS-DOS and Windows setup programs create all
the libraries and other required files.
Targeting Microsoft Windows
---------------------------
If you want to use C7 for OS/2 to create applications for the
Microsoft Windows operating system (or both Windows and MS-DOS):
1. Boot under MS-DOS and start Windows version 3.0 or later.
2. From the Program Manager, run the SETUP program for C7 for
MS-DOS and Windows. Install the compiler, targeting Windows.
Create the libraries you will use.
3. Exit Windows.
4. Run the INSTALL program for the Windows 3.1 Software Development
Kit (SDK) to install the SDK.
5. Delete any C7 for MS-DOS and Windows components you do not plan
to use. If you do not plan to compile or test any programs in
MS-DOS or Windows, you can delete the BIN, DEBUG, and NODEBUG
subdirectories under the C700 directory. If there are any Windows
or MS-DOS hosted utilities that you do not plan to use, consult
the PACKING.TXT (not PACKING.OS2) file to determine which files
you can delete.
6. Run the SETUP program for C7 for OS/2 to install C7 for OS/2. The
C7 for OS/2 SETUP program runs with MS-DOS or with OS/2 in an
MS-DOS or OS/2 session. If you are using OS/2 version 1.1, you
must run SETUP in an MS-DOS session.
Targeting MS-DOS Only
---------------------
If you want to use C7 for OS/2 to create applications for the MS-DOS
operating system only:
1. Boot under OS/2 or MS-DOS. Exit Windows if it is running.
2. Run the CSETUP program for C7 for MS-DOS and Windows. Run CSETUP
using the /X option; this will prevent CSETUP from modifying your
MS-DOS configuration files.
3. Delete any C7 for MS-DOS and Windows components you do not plan
to use. If you do not plan to compile or test any programs in
MS-DOS, you can delete the BIN subdirectory under the C700
directory. If there are any MS-DOS hosted utilities that you do
not plan to use, consult the PACKING.TXT (not PACKING.OS2) file
to determine which files you can delete.
4. Run the SETUP program for C7 for OS/2 to install C7 for OS/2. The
C7 for OS/2 SETUP program runs with MS-DOS or with OS/2 in an
MS-DOS or OS/2 session. If you are using OS/2 version 1.1, you
must run SETUP in an MS-DOS session.
Setting Environment Variables
-----------------------------
You must set your OS/2 environment variables before using C7 for OS/2.
The INCLUDE, INIT, LIB, PATH, TMP, and HELPFILES variables must be
set. These variables are explained on page 18 of the Microsoft C/C++
Getting Started book. The LIBPATH variable may also need to be
changed.
During installation of C7 for MS-DOS and Windows, a file named
AUTOEXEC.C70 is created in the INIT subdirectory of the C7 for MS-DOS
and Windows directory (C:\C700 by default). You can use the
environment variables set in that file as a model for the settings you
make in your OS/2 CONFIG.SYS file or another command file.
- The INCLUDE, LIB, and HELPFILES variables should be the same in C7
for OS/2 and C7 for MS-DOS and Windows. For example:
SET INCLUDE=C:\C700\INCLUDE;C:\C700\MFC\INCLUDE
SET LIB=C:\C700\LIB;C:\C700\MFC\LIB
SET HELPFILES=C:\C700\HELP\*.HLP
- The INIT variable should be the same in C7 for OS/2 and C7 for
MS-DOS and Windows if you want to keep the same settings for the
Programmer's WorkBench in each operating system. For example:
SET INIT=C:\C700\INIT
- The PATH variable should contain the BINP and BINB subdirectories
under the base directory that you specified when you installed C7
for OS/2 (C:\C700 by default). Make sure the BIN subdirectory under
the C700 base directory is not on your path. For example:
PATH=C:\C700\BINP;C:\C700\BINP;C:\OS2;C:\OS2\SYSTEM
- The MSHELP.DLL file is installed in the DLL subdirectory under the
base C700 directory. OS/2 must be able to find this file. Either
copy MSHELP.DLL to a directory specified by the LIBPATH variable,
or add the DLL subdirectory under the C700 directory to the LIBPATH
variable entry. For example:
LIBPATH=C:\OS2\DLL;C:\C700\DLL
=======================< Part 3: Product Notes >===========================
Programmer's WorkBench (PWB)
----------------------------
To use PWB, you must use OS/2 version 1.2 or later.
The OS/2 version of PWB is slightly different from the MS-DOS version.
Some tasks, such as Build and Search, are run as background processes.
You can use PWB while it carries out a search or is building a
program.
For some tasks, the OS/2 hosted version of PWB is not as fast as the
MS-DOS hosted version. For example, the functions for arranging PWB
windows take longer with OS/2 than with MS-DOS.
The PWB extensions for MS-DOS cannot be used with OS/2. C7 for OS/2
provides OS/2 specific PWB extensions. The OS/2 files have the
extension .PXT, instead of the .MXT extension used by the MS-DOS
version of PWB.
Extensions to PWB version 2.0 cannot be created with C7 for OS/2.
Three functions are provided in the OS/2 version to cancel background
processes. These are described below:
- Cancel Build
Usage: arg meta compile
The Cancel Build function (on the Run menu) stops the current
background build or compile and flushes any queued build
operations.
- Cancel Search
Usage: cancelsearch
Returns: TRUE if there was a search in progress and it was
canceled; otherwise, it returns FALSE.
The Cancel Search function (on the Search menu) cancels the
background search. The search log contains the partial results of
the aborted search and is not flushed.
- Cancel Print
Usage: meta arg print
The Cancel Print (on the File menu) cancels the current print job.
Using Precompiled Headers
-------------------------
Precompiled headers that have been compiled using C7 for MS-DOS and
Windows cannot be used by C7 for OS/2. You must compile the header
again using C7 for OS/2 before it can be included as a precompiled
header for C7 for OS/2.
Building Windows Help Files
---------------------------
The Windows Help Compilers (HC31.EXE and HC30.EXE) supplied with the
SDK cannot be run with OS/2. You may be able to use a Help Compiler in
an MS-DOS session if your OS/2 configuration provides enough memory to
the MS-DOS session. If you cannot use the Help Compiler in an MS-DOS
session with OS/2, reboot under MS-DOS to use the Help Compiler.
Because the Help Compiler does not run with OS/2, you cannot build the
HELPEX example using the makefile provided with the SDK.
How to Get Product Assistance
-----------------------------
Consult the Product Assistance Request form at the back of the C/C++
Run-Time Library Reference.
===========================================================================
Microsoft and MS-DOS are registered trademarks, and Windows is a
trademark of Microsoft Corporation.
OS/2 is a registered trademark licensed to Microsoft Corporation.