Overview
Comment: | Updated notes about kitsh
Added notes about plugability |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: | 5421b32beb807978cfedbaa3f1ff8b8e050597ca |
User & Date: | rkeene on 2011-07-02 12:03:53 |
Other Links: | manifest | tags |
Context
2011-07-04
| ||
21:15 | Added support for forcing build check-in: 37fc9e9fae user: rkeene tags: trunk | |
2011-07-02
| ||
12:03 |
Updated notes about kitsh
Added notes about plugability check-in: 5421b32beb user: rkeene tags: trunk | |
2011-06-24
| ||
18:44 | Upgraded test suite to use Tcl/Tk 8.5.10 check-in: 75999463a7 user: rkeene tags: trunk | |
Changes
Modified README from [f55796d36b] to [5d77e30af0].
197 197 responsible for downloading the source code for the appropriate version that 198 198 will compile and link against the current version of Tcl (user requested 199 199 version can be found in "TCLVERS", while the actual version must be requested 200 200 from the "tclConfig.sh" script), compiling it, installing a functional copy 201 201 into the per-project "inst" directory, and installing anything that needs to 202 202 be in the Tclkit's VFS root into the per-project "out" directory. 203 203 204 -The exception to this is the "kitsh" and "kitdll" projects. They are the glue 205 -that binds all the individual projects together into a single executable. Its 206 -build script does not create an "inst" or an "out" directory because it is not 207 -a library. Instead, it collects all the other project's "out" directories 208 -into a single directory (starpack.vfs), as well a static file (boot.tcl). 209 -It then compiles the source code, and then installs the VFS onto the resulting 210 -executable. The VFS is created by the "installvfs.tcl" script for Kitsh. For 211 -KitDLL the VFS is created by "dir2c.tcl". 204 +Any additional projects can be included simply by creating the appropriate 205 +directory in the same directory as the "kitcreator" script, creating a 206 +"build.sh" script in that directory that follows the above procedure, and then 207 +referencing that directory in "KITCREATOR_PKGS" for the "kitcreator" invocation. 208 +In this way KitCreator is "pluggable". Included packages may be either 209 +statically or dynamically linked. If it is statically linked then the module 210 +name must be the name of the directory -- that is, if the directory were "foo", 211 +KitCreator will expect to initialize the module statically using Foo_Init(). 212 + 213 +The exception to this is the "kitsh" project. It is the glue that binds all 214 +the individual projects together into a single executable. Its build script 215 +does not create an "inst" or an "out" directory because it is not a library. 216 +Instead, it collects all the other project's "out" directories into a single 217 +directory (starpack.vfs), as well a static file (boot.tcl). It then compiles 218 +the source code, and then installs the VFS onto the resulting executable. 219 +The VFS is created by the "installvfs.tcl" script for Kitsh. For KitDLL the 220 +VFS is created by "dir2c.tcl". 212 221 213 222 If the "mk4tcl" project fails to build (or is not requested to be built), 214 223 the rest of the project will be built using zip files instead of Metakit 215 224 databases. 216 225 217 226 To create the storage database, one of two Tclkits is used (tried in this 218 227 order):