Dec 192017
 
CMAKE 1.00 - The best MAKE for MSC/WIN SDK: Executable & Samples.
File CM100EXE.ZIP from The Programmer’s Corner in
Category C Source Code
CMAKE 1.00 – The best MAKE for MSC/WIN SDK: Executable & Samples.
File Name File Size Zip Size Zip Type
CMAKE.EXE 79519 32494 deflated
FILELIST.TXT 3389 686 deflated
README.TXT 5975 2053 deflated
SAMPLES 0 0 stored
SAMPLES.TXT 5332 1051 deflated
C 0 0 stored
CFG 0 0 stored
CMAKE.CFG 570 250 deflated
README.TXT 1254 386 deflated
CMDDEF 0 0 stored
CMAKE.CFG 94 86 deflated
MAKEFILE 1149 383 deflated
README.TXT 992 431 deflated
SORTSUM.BAT 157 112 deflated
SOURCE1.TXT 15 15 stored
SOURCE2.TXT 18 18 stored
CMDEQUIV 0 0 stored
1.TXT 99 48 deflated
CMAKE.CFG 125 107 deflated
MAKEFILE 1558 424 deflated
README.TXT 1178 478 deflated
COPY 0 0 stored
MAKEFILE 2475 469 deflated
README.TXT 473 254 deflated
SRC 0 0 stored
1.SRC 41 41 stored
2.SRC 41 41 stored
MORE 0 0 stored
3.SRC 46 46 stored
TRG 0 0 stored
1.TRG 41 40 deflated
GREETING.C 230 152 deflated
GREETING.H 71 63 deflated
GREETING.LNK 60 54 deflated
HELLO.C 173 133 deflated
HELLO.H 73 62 deflated
MAKEFILE 3755 727 deflated
MESSAGE.LRF 46 42 deflated
README.TXT 2108 737 deflated
WORLD.C 173 133 deflated
WORLD.H 73 62 deflated
IF 0 0 stored
GREETING.C 203 130 deflated
GREETING.H 71 63 deflated
GREETING.LNK 60 54 deflated
HELLO.C 146 110 deflated
HELLO.H 73 62 deflated
MAKEFILE 3472 720 deflated
MESSAGE.LRF 46 42 deflated
README.TXT 438 235 deflated
WORLD.C 146 110 deflated
WORLD.H 73 62 deflated
MASM 0 0 stored
A_HELLO.ASM 235 155 deflated
A_HELLO.H 81 66 deflated
A_WORLD.ASM 235 156 deflated
A_WORLD.H 81 66 deflated
GREETING.C 238 154 deflated
GREETING.H 71 63 deflated
GREETING.LNK 60 54 deflated
HELLO.C 173 133 deflated
HELLO.H 73 62 deflated
HELLO.INC 70 62 deflated
MAKEFILE 5045 849 deflated
MESSAGE.LRF 84 53 deflated
README.TXT 2952 834 deflated
WORLD.C 173 133 deflated
WORLD.H 73 62 deflated
WORLD.INC 70 62 deflated
WINDOWS 0 0 stored
HW.C 4111 996 deflated
HW.DEF 354 224 deflated
HW.DLG 1232 350 deflated
HW.H 515 180 deflated
HW.ICO 1718 251 deflated
HW.LNK 92 66 deflated
HW.RC 276 193 deflated
MAKEFILE 2776 606 deflated
README.TXT 3044 993 deflated

Download File CM100EXE.ZIP Here

Contents of the README.TXT file


README.TXT


WHAT IS CMAKE?:

CMAKE is a program maintenance utility designed especially for the
Microsoft(R) C and Microsoft Windows(TM) programmer. For the
commands:

CL, LIB, LINK, MASM, RC, and COPY,

CMAKE automatically determines all dependencies directly from the
command line.


DISTRIBUTION FILES:

CMAKE is distributed as three self-extracting archive files.

CM100EXE.EXE - Executable and Samples.

This is all you need to get started, but you should
seriously consider getting, CM100HLP.EXE, if you
don't already have it.

CM100HLP.EXE - Microsoft QuickHelp-Compatible Help File.

This is the complete manual for CMAKE. It can be
viewed with the program, QH.EXE, which is
distributed with the Microsoft C Optimizing
Compiler 6.00 and the Microsoft Macro Assembler
6.00. The CMAKE help file is similar in style to
the QuickHelp files that Microsoft distributes with
its C and Assembler packages.

CM100TXT.EXE - ASCII Text-File Version of the Help File in
CM100HLP.EXE.

The information contained in this file is identical
to that of CM100HLP.EXE. It is only included for
those users who either do not have the Microsoft
QuickHelp program, QH.EXE, or would like a
printable version of the CMAKE help file.


INSTALLATION:

To install CMAKE,

1. Create a directory for CMAKE on the target drive.
2. Copy your distribution files into the newly created directory.
3. Execute the self-extracting distribution files (in any order).


PRINTING THE DOCUMENTS:

The following command may be used to print the document files
that are included with CMAKE 1.00:

copy *.txt prn


GETTING STARTED:

1. PUT CMAKE.EXE IN YOUR PATH

2. REVIEW THE SAMPLES

The sample programs will teach you how to use CMAKE to maintain
your application. In addition, the samples provide make files,
LIB response files, and LINK response files that you may use as
templates for your application.

The CMAKE QuickHelp file provides a convenient way to study the
samples. If you select "Samples" from the CMAKE Contents
screen, you will be able to view all of the samples files
provided with CMAKE.

The sample in the directory, SAMPLE\C, will probably be of
interest to everyone. This sample will show you how to use
CMAKE to maintain an application that is built with the
Microsoft C programs: CL, LIB, and LINK.

If you are a Microsoft Windows programmer, study the sample in
the directory, SAMPLE\WINDOWS.


If you use MASM, review the sample in the directory,
SAMPLE\MASM.

If you would like to know how to expand CMAKE's command
vocabulary (beyond CL, LIB, LINK, MASM, RC, COPY, SET, and
REM), you should review the samples in the directories,
SAMPLE\CMDDEF and SAMPLE\CMDEQUIV.

The sample in the directory, SAMPLE\CFG, contains a
configuration file that gives a complete list of all possible
configuration statements.

If you have a situation where you would like to explicitly
specify dependencies (as you would with a generic make
utility), review the sample in the directory, SAMPLE\IF.

If you would like to know how CMAKE handles the MS-DOS(R) COPY
command, you should review the sample in the directory,
SAMPLE\COPY.


For each sample that you study, you should:

- Read the files, "README.TXT" and "MAKEFILE", that are
included with the sample.
- Run CMAKE on the sample.
- Touch/modify some source files and run CMAKE again to see
how well CMAKE automatically determines which commands
are required to renew the sample application.


3. USE QUICK HELP (QH.EXE) TO VIEW THE HELP FILE

The help file, CMAKE.HLP, is compatible with Microsoft's
QuickHelp Facility. (The QuickHelp facility, QH.EXE, is
distributed with the Microsoft C Optimizing Compiler 6.00 and
the Microsoft Macro Assembler 6.00. If you do not have QH.EXE,
you can use the file, CMAKE.TXT, which is the ASCII text-file
version of the file, CMAKE.HLP, and is contained in the
distribution file, CM100TXT.EXE.)

Add the path of the file, CMAKE.HLP, to your HELPFILES
environment variable. To view the help for CMAKE:

a. Run CMAKE with the /help (or equivalently /h) option:

cmake /h

or

b. Run the QuickHelp program by using the command:

qh cmake

or

c. Run the QuickHelp program by using the command:

qh

and select CMAKE from the "Categories" menu, or search for
the topic, "cmake" (press S and enter the topic, cmake).

Note that since QH will only open the first 15 files found in
the directories given by the HELPFILES environment variable,
you might have to list the CMAKE help directory first. If QH
does not open CMAKE.HLP automatically, you will have to
manually open this help file/database after you start QH.

-----------------------------------------------------------------
Microsoft and MS-DOS are registered trademarks of Microsoft
Corporation.

Windows is a trademark of Microsoft Corporation.
CONFIGURATION FILE SAMPLE

This sample demonstrates all the possible types of statements that
may be used in a CMAKE configuration file.

NOTE THE FOLLOWING IN THE FILE, "cmake.cfg":

1. The comments.

See: The CMAKE Configuration File
* Comments in the Configuration File
in the help file.

2. The section tag, [CMAKE].

See: The CMAKE Configuration File
* The CMAKE Section Tag in the Configuration File
in the help file.

3. The assignment statements. "cmake.cfg" gives a complete list
of the Boolean variables that may be used in a
configuration file. In this sample, each Boolean variable is
set to its default value.

See: The CMAKE Configuration File
* Assignment Statements in the Configuration File
in the help file.

4. The command-definition statement.

See: The CMAKE Configuration File
* Command-Definition Statements
in the help file.

5. The command-equivalence statement.

See: The CMAKE Configuration File
* Command-Equivalence Statements
in the help file.
COMMAND-DEFINITION STATEMENT SAMPLE

This sample demonstrates how to add a new command to CMAKE's
vocabulary through the use of a command-definition statement in
the configuration file, "cmake.cfg".


TO RUN CMAKE:

Execute CMAKE by entering the command

cmake

No parameters are required.


NOTE THE FOLLOWING:

1. The commands (and comments) in the make file, "makefile".
CMAKE will deduce all dependencies from these commands.

See: The Make File for CMAKE
User-Defined Commands
* When is a User-Defined Command Required?
in the help file.

2. The command-definition statement and section tag, [CMAKE], in
the configuration file, "cmake.cfg".

See: The CMAKE Configuration File
* Command-Definition Statements
* The CMAKE Section Tag in the Configuration File
in the help file.
COMMAND-EQUIVALENCE STATEMENT SAMPLE

This sample demonstrates how to add a new command to CMAKE's
vocabulary through the use of a command-equivalence statement in
the configuration file, "cmake.cfg".


TO RUN CMAKE:

Execute CMAKE by entering the command

cmake

No parameters are required.


NOTE THE FOLLOWING:

1. The commands (and comments) in the make file, "makefile".
CMAKE will deduce all dependencies from these commands.

See: The Make File for CMAKE
User-Defined Commands
* When is a User-Defined Command Required?
Equivalent Commands
* How CMAKE Processes an Equivalent Command
in the help file.

2. The command-equivalence statement, command-definition
statement, and section tag, [CMAKE], in the configuration file,
"cmake.cfg".

See: The CMAKE Configuration File
* Command-Equivalence Statements
* Command-Definition Statements
* The CMAKE Section Tag in the Configuration File
in the help file.
COPY SAMPLE

This sample demonstrates how CMAKE handles the COPY command.


TO RUN CMAKE:

Execute CMAKE by entering the command

cmake

No parameters are required.


NOTE THE FOLLOWING:

The commands (and comments) in the make file, "makefile".
CMAKE will deduce all dependencies from these commands.

See: The Make File for CMAKE
* COPY
in the help file.
MICROSOFT C OPTIMIZING COMPILER SAMPLE

This sample demonstrates how to use CMAKE to maintain a DOS
application that is built with the programs: CL, LIB, and LINK.


TO RUN CMAKE:

Execute CMAKE by entering the command

cmake

No parameters are required.


NOTE THE FOLLOWING:

1. The commands (and comments) in the make file, "makefile".
CMAKE will deduce all dependencies from these commands.

See: The Make File for CMAKE
CL
* When is a CL Command Required?
LIB
* When is a LIB Command Required?
LINK
* When is a LINK Command Required?
in the help file.

2. The format of the LIB response file, "message.lrf". CMAKE
requires that a response file (of a particular form) be used
with the LIB command.

See: The Make File for CMAKE
LIB
* The LIB Command Line
in the help file.

3. The format of the LINK response file, "greeting.lnk". CMAKE
requires that a response file (of a particular form) be used
with the LINK command.

See: The Make File for CMAKE
LINK
* The LINK Command Line
in the help file.

4. The use and placement of the comment

/* CMAKE - INCLUDE END */

in the files, "hello.c", "world.c", and "greeting.c".

In these files, this comment is placed after all #include
statements. Although this comment is not required in C-source
files, it serves as an end-of-file mark for CMAKE, and thus
prevents CMAKE from searching the entire source file for
#include statements.

See: Optimizing Performance
* Use the End-of-Includes Comment in Your Source Files
The Make File for CMAKE
CL
* Switches for CL
* How CMAKE Processes a C-Source File
in the help file.
IF STATEMENT SAMPLE

This sample demonstrates how to use if statements in a make file.


TO RUN CMAKE:

Execute CMAKE by entering the command

cmake

No parameters are required.


NOTE THE FOLLOWING:

The if statements (and comments) in the make file, "makefile".

See: The Make File for CMAKE
* The if Statement
in the help file.
MICROSOFT MACRO ASSEMBLER SAMPLE

This sample demonstrates how to use CMAKE to maintain a DOS
application that is built with the programs: MASM, CL, LIB, and
LINK.


TO RUN CMAKE:

Execute CMAKE by entering the command

cmake

No parameters are required.


NOTE THE FOLLOWING:

1. The commands (and comments) in the make file, "makefile".
CMAKE will deduce all dependencies from these commands.

See: The Make File for CMAKE
MASM
* When is a MASM Command Required?
CL
* When is a CL Command Required?
LIB
* When is a LIB Command Required?
LINK
* When is a LINK Command Required?
in the help file.

2. The format of the LIB response file, "message.lrf". CMAKE
requires that a response file (of a particular form) be used
with the LIB command.

See: The Make File for CMAKE
LIB
* The LIB Command Line
in the help file.

3. The format of the LINK response file, "greeting.lnk". CMAKE
requires that a response file (of a particular form) be used
with the LINK command.

See: The Make File for CMAKE
LINK
* The LINK Command Line
in the help file.

4. The use and placement of the comment

; CMAKE - INCLUDE END

in the files, "a_hello.asm" and "a_world.asm".

In these files, this comment is placed after all include
statements. Although this comment is not required in assembly-
language-source files, it serves as an end-of-file mark for
CMAKE, and thus prevents CMAKE from searching the entire source
file for include statements.

See: Optimizing Performance
* Use the End-of-Includes Comment in Your Source Files
The Make File for CMAKE
MASM
* Switches for MASM
* How CMAKE Processes an Assembly-Language-Source File
in the help file.

5. The use and placement of the comment

/* CMAKE - INCLUDE END */

in the files, "hello.c", "world.c", and "greeting.c".

In these files, this comment is placed after all #include
statements. Although this comment is not required in C-source
files, it serves as an end-of-file mark for CMAKE, and thus
prevents CMAKE from searching the entire source file for
#include statements.

See: Optimizing Performance
* Use the End-of-Includes Comment in Your Source Files
The Make File for CMAKE
CL
* Switches for CL
* How CMAKE Processes a C-Source File
in the help file.
MICROSOFT WINDOWS SOFTWARE DEVELOPMENT KIT SAMPLE

This sample demonstrates how to use CMAKE to maintain a Microsoft
Windows application that is built with the programs: CL, RC, and
LINK.


TO RUN CMAKE:

1. Check the LINK response file, "hw.lrf", to be sure that the
paths of the libraries, "libw.lib" and "slibcew.lib", are
correct.
2. Execute CMAKE by entering the command

cmake

No parameters are required.


NOTE THE FOLLOWING:

1. The commands (and comments) in the make file, "makefile".
CMAKE will deduce all dependencies from these commands.

See: The Make File for CMAKE
CL
* When is a CL Command Required?
RC
RC/C - Compile a Resource-Script File
* When is an RC/C Command Required?
RC
RC/A - Add a Resource File to an Executable File
* When is an RC/A Command Required?
LINK
* When is a LINK Command Required?
in the help file.

2. The format of the LINK response file, "hw.lnk". CMAKE requires
that a response file (of a particular form) be used with the
LINK command.

See: The Make File for CMAKE
LINK
* The LINK Command Line
in the help file.

Since CMAKE does not use the LIB environment variable, the
paths of the windows libraries, "libw.lib" and "slibcew.lib"
must be provided.

3. The use and placement of the comment

/* CMAKE - INCLUDE END */

in the files, "hw.c" and "hw.rc".

In the file, "hw.c", this comment is placed after all #include
statements. Although this comment is not required in C-source
files, it serves as an end-of-file mark for CMAKE, and thus
prevents CMAKE from searching the entire source file for
#include statements.

See: Optimizing Performance
* Use the End-of-Includes Comment in Your Source Files
The Make File for CMAKE
CL
* Switches for CL
* How CMAKE Processes a C-Source File
in the help file.

In the file, "hw.rc", this comment is placed after all #include
statements and resource-include statements (i.e. ICON, BITMAP,
CURSOR, FONT, or user-defined resource statements). This
comment is required in this file.

See: The Make File for CMAKE
RC
RC/C - Compile a Resource-Script File
Helpful Hints
* Controlling Resource-Script File Processing
* Switches for RC
* How CMAKE Processes a Resource-Script File
Optimizing Performance
* Use the End-of-Includes Comment in Your Source Files
in the help file.


 December 19, 2017  Add comments

Leave a Reply