Overview
| Comment: | Simplify and fix handling of 'kit.exe' instead of 'kit' on Windows. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: | 31baf7fa49ab40d1013dbcd31994945a20470714 |
| User & Date: | mistachkin on 2015-10-07 22:44:37 |
| Other Links: | manifest | tags |
Context
|
2015-10-08
| ||
| 18:29 | Do not delete the Kit DLL after building it. check-in: 65edae117a user: mistachkin tags: trunk | |
|
2015-10-07
| ||
| 22:44 | Simplify and fix handling of 'kit.exe' instead of 'kit' on Windows. check-in: 31baf7fa49 user: mistachkin tags: trunk | |
| 02:38 | Fix hard-coded use of './kit' in the kitsh build script and improve how the kit target name is defined. check-in: f84245cd51 user: mistachkin tags: trunk | |
Changes
Modified kitsh/build.sh from [d9a8c3dd79] to [daac00effa].
182 182 if [ -f "tclsh.exe" ]; then 183 183 mv tclsh.exe kit.exe 184 184 else 185 185 mv tclsh kit 186 186 fi 187 187 else 188 188 ## The executable is always named "kit" 189 - if [ -f 'kit.exe' -a ! -f 'kit' ]; then 189 + if [ -f 'kit.exe' ]; then 190 190 KITTARGET_NAME='./kit.exe' 191 191 else 192 192 KITTARGET_NAME='./kit' 193 193 fi 194 194 fi 195 195 export KITTARGET_NAME 196 196 ................................................................................ 222 222 ## Install using Tclsh, which may work if we're not using Metakit 223 223 ### Call installer 224 224 echo "Running: \"${TCLSH_NATIVE}\" installvfs.tcl \"${KITTARGET_NAME}\" starpack.vfs \"${ENABLECOMPRESSION}\" \"${KITTARGET_NAME}.new\"" 225 225 "${TCLSH_NATIVE}" installvfs.tcl "${KITTARGET_NAME}" starpack.vfs "${ENABLECOMPRESSION}" "${KITTARGET_NAME}.new" || exit 1 226 226 fi 227 227 fi 228 228 229 - cat "${KITTARGET_NAME}.new" > "${KITTARGET_NAME}" || exit 1 229 + cp "${KITTARGET_NAME}.new" "${KITTARGET_NAME}" 230 230 rm -f "${KITTARGET_NAME}.new" 231 231 232 232 # Cleanup 233 233 if [ "${KITTARGET}" = "kitdll" ]; then 234 234 ## Remove built interpreters if we are building KitDLL -- 235 235 ## they're just tiny stubs anyway 236 236 rm -f "${KITTARGET_NAME}" 237 237 fi 238 238 239 239 exit 0 240 240 ) || exit 1 241 241 242 242 exit 0