Overview
Comment: | Added documentation on KitDLL SDK |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | tcl-sdk-support |
Files: | files | file ages | folders |
SHA1: | 6f5ce08b75eb9bc839343a53e026a17457230c1a |
User & Date: | rkeene on 2011-11-14 05:01:10 |
Other Links: | manifest | tags |
Context
2011-11-14
| ||
07:10 |
Updated to include sub-directories from header files (for Win32 support)
Fixed issue with regexp used to replace refernces to -ltcl/-ltk for KitDLL SDK Fixed issue with selecting library file on Win32 Updated to pull libraries from KitSH for KitDLL SDK to avoid picking wrong file if one is already in the current directory check-in: fe142d1843 user: rkeene tags: tcl-sdk-support | |
05:01 | Added documentation on KitDLL SDK check-in: 6f5ce08b75 user: rkeene tags: tcl-sdk-support | |
04:29 | Updated to ignore created SDKs when looking for created kits during test builds check-in: cb0c37e35e user: rkeene tags: tcl-sdk-support | |
Changes
Modified README from [5d77e30af0] to [cb012f0bd1].
137 137 itcl thread 138 138 139 139 Kitsh Configure Options: 140 140 1. --enable-kit-storage={zip|mk4|auto} 141 141 Specify which type of storage to use with the Tclkit. The 142 142 default is to auto-detect. Auto-detection uses Mk4 if 143 143 available and built statically, otherwise it falls back to Zip. 144 + 145 +-------------------- 146 +Using the KitDLL SDK 147 +-------------------- 148 +When you build a KitDLL, a "kitdll-sdk-<tclvers>.tar.gz" tarball is also 149 +produced. This tarball contains the Tcl (and Tk, if compiled) stubs libraries, 150 +and Tcl (and Tk, if compiled) header files needed to compile and link things 151 +against Tcl (and Tk). It also includes "tclConfig.sh" (and "tkConfig.sh", if 152 +Tk was compiled). 153 + 154 +The purpose for this tarball is to be used to build Tcl extensions or 155 +applications that rely on Tcl/Tk using the KitDLL. 156 + 157 +To use it, one first must extract the tarball. After that the environment 158 +variable "TCLKIT_SDK_DIR" must be set to the directory that was created in 159 +order to make most of the variables contain useful values. 160 + 161 +For example, to build an extension using the KitDLL SDK one would typically do 162 +something like: 163 + 1. Compile KitDLL (may be omitted if the KitDLL SDK is already 164 + available) 165 + a. $ KITCREATOR_PKGS='tk itcl kitdll' 166 + b. $ export KITCREATOR_PKGS 167 + c. $ ./kitcreator 168 + 2. Compile the Extension 169 + a. $ tar -xf /path/to/libtclkit-sdk-8.4.19.tar.gz 170 + b. $ TCLKIT_SDK_DIR="$(pwd)/libtclkit-sdk-8.4.19" 171 + c. $ export TCLKIT_SDK_DIR 172 + d. $ ./configure --with-tcl="${TCLKIT_SDK_DIR}/lib" 173 + e. $ make 144 174 145 175 ------------------- 146 176 Method of Operation 147 177 ------------------- 148 178 Summary: 149 179 1. "kitcreator" calls */build.sh 150 180 2. */build.sh downloads and compiles appropriate software