Differences From Artifact [5d77e30af0]:
- File
README
— part of check-in
[5421b32beb]
at
2011-07-02 12:03:53
on branch trunk
— Updated notes about kitsh
Added notes about plugability (user: rkeene, size: 10032) [annotate] [blame] [check-ins using]
To Artifact [d6d6daf628]:
- File README — part of check-in [8d015538ad] at 2011-11-14 16:42:15 on branch tcl-sdk-support — Corrected typo (user: rkeene, size: 11247) [annotate] [blame] [check-ins using] [more...]
︙ | ︙ | |||
137 138 139 140 141 142 143 144 145 146 147 148 149 150 | itcl thread Kitsh Configure Options: 1. --enable-kit-storage={zip|mk4|auto} Specify which type of storage to use with the Tclkit. The default is to auto-detect. Auto-detection uses Mk4 if available and built statically, otherwise it falls back to Zip. ------------------- Method of Operation ------------------- Summary: 1. "kitcreator" calls */build.sh 2. */build.sh downloads and compiles appropriate software | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 | itcl thread Kitsh Configure Options: 1. --enable-kit-storage={zip|mk4|auto} Specify which type of storage to use with the Tclkit. The default is to auto-detect. Auto-detection uses Mk4 if available and built statically, otherwise it falls back to Zip. -------------------- Using the KitDLL SDK -------------------- When you build a KitDLL, a "libtclkit-sdk-<tclvers>.tar.gz" tarball is also produced. This tarball contains the Tcl (and Tk, if compiled) stubs libraries, and Tcl (and Tk, if compiled) header files needed to compile and link things against Tcl (and Tk). It also includes "tclConfig.sh" (and "tkConfig.sh", if Tk was compiled). The purpose for this tarball is to be used to build Tcl extensions or applications that rely on Tcl/Tk using the KitDLL. To use it, one first must extract the tarball. After that the environment variable "TCLKIT_SDK_DIR" must be set to the directory that was created in order to make most of the variables contain useful values. For example, to build an extension using the KitDLL SDK one would typically do something like: 1. Compile KitDLL (may be omitted if the KitDLL SDK is already available) a. $ KITCREATOR_PKGS='tk itcl kitdll' b. $ export KITCREATOR_PKGS c. $ ./kitcreator 2. Compile the Extension a. $ tar -xf /path/to/libtclkit-sdk-8.4.19.tar.gz b. $ TCLKIT_SDK_DIR="$(pwd)/libtclkit-sdk-8.4.19" c. $ export TCLKIT_SDK_DIR d. $ ./configure --with-tcl="${TCLKIT_SDK_DIR}/lib" e. $ make ------------------- Method of Operation ------------------- Summary: 1. "kitcreator" calls */build.sh 2. */build.sh downloads and compiles appropriate software |
︙ | ︙ |