Check-in [6ad3fbe8a5]
Overview
Comment:Fixed typo
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1:6ad3fbe8a5ed28260309f3bb6025e5d7a05424be
User & Date: rkeene on 2010-09-26 04:39:52
Other Links: manifest | tags
Context
2010-09-26
04:39
Updated to build under i586-mingw32msvc check-in: 19963bc8da user: rkeene tags: trunk
04:39
Fixed typo check-in: 6ad3fbe8a5 user: rkeene tags: trunk
04:39
Enabled Mk4vfs compression

Added appropriate licensing information.

Updated README check-in: 2203d001cd user: rkeene tags: trunk

Changes

Modified README from [6d75316e4a] to [f4f19cabd3].

110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
	5. It uses GNU Autoconf scripts for compiling the part of the Tclkit
	   that brings the whole thing together (the Kitsh)

To accomplish these goals the following mechanisms are in place:
	1. The top-level "kitcreator" script; and
	2. Per-project subdirectories, each containing a "build.sh" script

The top-level "kitcreator" script is very simple.  It's only job is to
interpret command line arguments, and call the per-project "build.sh" scripts.
For the "tcl" project it also finds the appropriate "tclConfig.sh" (and stores
this path in TCLCONFIGDIR) to enable subsequent build scripts to find the
appropriate Tcl to link against.

The per-project "build.sh" scripts are entirely autonomous.  They are
responsible for downloading the source code for the appropriate version that







|







110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
	5. It uses GNU Autoconf scripts for compiling the part of the Tclkit
	   that brings the whole thing together (the Kitsh)

To accomplish these goals the following mechanisms are in place:
	1. The top-level "kitcreator" script; and
	2. Per-project subdirectories, each containing a "build.sh" script

The top-level "kitcreator" script is very simple.  Its only job is to
interpret command line arguments, and call the per-project "build.sh" scripts.
For the "tcl" project it also finds the appropriate "tclConfig.sh" (and stores
this path in TCLCONFIGDIR) to enable subsequent build scripts to find the
appropriate Tcl to link against.

The per-project "build.sh" scripts are entirely autonomous.  They are
responsible for downloading the source code for the appropriate version that