summaryrefslogtreecommitdiffstats
path: root/win/README
diff options
context:
space:
mode:
authordavygrvy <davygrvy@pobox.com>2001-11-15 00:19:40 (GMT)
committerdavygrvy <davygrvy@pobox.com>2001-11-15 00:19:40 (GMT)
commit8ffab5be65201e8b32d550fa8f49b0387e2571cd (patch)
treeb7174dff3f6bfc558a9dd5a6b4f52d8cd980de8c /win/README
parent49fe76ced5db356a7f65c413e66fbf669b912370 (diff)
downloadtcl-8ffab5be65201e8b32d550fa8f49b0387e2571cd.zip
tcl-8ffab5be65201e8b32d550fa8f49b0387e2571cd.tar.gz
tcl-8ffab5be65201e8b32d550fa8f49b0387e2571cd.tar.bz2
* win/makefile.vc:
* win/rules.vc: Small bug fixes. * win/README: added some docs pointing to the docs in makefile.vc for it's use.
Diffstat (limited to 'win/README')
-rw-r--r--win/README19
1 files changed, 12 insertions, 7 deletions
diff --git a/win/README b/win/README
index 0d4a026..e4013f6 100644
--- a/win/README
+++ b/win/README
@@ -1,6 +1,6 @@
Tcl 8.4 for Windows
-RCS: @(#) $Id: README,v 1.23 2001/11/07 23:37:52 mdejong Exp $
+RCS: @(#) $Id: README,v 1.24 2001/11/15 00:19:41 davygrvy Exp $
1. Introduction
---------------
@@ -38,13 +38,18 @@ In order to compile Tcl for Windows, you need the following items:
place /usr/local/mingw/bin at the front of your PATH env var.
-In practice, this release is built with Visual C++ 6.0
+In practice, this release is built with Visual C++ 6.0 and the TEA
+Makefile.
-In the "win" subdirectory of the source release, you will find
-"makefile.vc". This is the makefile Visual C++ compiler. You should
-update the paths at the top of the file to reflect your system
-configuration. Now you can use "make" (or "nmake" for VC++) to build
-the tcl libraries and the tclsh executable.
+If you are building with Visual C++, in the "win" subdirectory of the
+source release, you will find "makefile.vc". This is the makefile for
+the Visual C++ compiler and uses the stock NMAKE tool. Detailed
+directions for using it, are in the comments of "makefile.vc". A quick
+example would be:
+ C:\tcl_source\win\>nmake -f makefile.vc
+
+There is also a Developer Studio workspace and project file, too, if you
+would like to use them.
If you are building with Cygwin, you can use the configure script
that lives in the win subdirectory. The Cygwin based configure/build