Overview
| Comment: | Minor documentation update (sync with Wiki) |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
38ada8ff4dd686a5de2a01f8a41ec7cc |
| User & Date: | rkeene on 2010-09-26 04:44:12 |
| Other Links: | manifest | tags |
Context
|
2010-09-26
| ||
| 04:44 | Fixed sync logic issue with new support for specifying which storage system to use (installvfs.tcl and kitInit.c) check-in: e5c8483726 user: rkeene tags: trunk | |
| 04:44 | Minor documentation update (sync with Wiki) check-in: 38ada8ff4d user: rkeene tags: trunk | |
| 04:44 |
KitCreator 0.3.1.x
Updated documentation regarding to new storage options check-in: ad81f6cde8 user: rkeene tags: trunk, 0.3.1 | |
Changes
Modified README from [fc6e6612a1] to [d727105047].
| ︙ | ︙ | |||
170 171 172 173 174 175 176 | the source code, and then installs the Metakit database containing the VFS onto the resulting executable. If the "mk4tcl" project fails to build (or is not requested to be built), the rest of the project will be built using zip files instead of Metakit databases. | | | | 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 | the source code, and then installs the Metakit database containing the VFS onto the resulting executable. If the "mk4tcl" project fails to build (or is not requested to be built), the rest of the project will be built using zip files instead of Metakit databases. To create the storage database, one of two Tclkits is used (tried in this order): 1. The Tclkit specified by the TCLKIT environment variable (or "tclkit" if that variable is not set) if it is functional; or 2. The built Tclkit itself The second method will not work if the built Tclkit is not executable on the current platform (i.e., in the case of cross-compilation) and so it may be necessary to bootstrap a runnable Tclkit first. |