View Ticket
Ticket UUID: ff1065968a01e239f5e5a882a3ec4c9423918b8d
Title: KitDLL needs to support static linking to Mk4tcl
Status: Closed Type: Code Defect
Severity: Important Priority: Medium
Subsystem: KitDLL (The libTclkit Core) Resolution: Fixed
Last Modified: 2010-10-06 16:47:56
Version Found In: 0.5.0
KitDLL will not initialize the Mk4tcl package if statically linked. We need to do this and also give the user some way to control the behaviour of Mk4tcl linking like we do with Tk. Default to dynamically linking it on KitDLL, statically linking it on Kitsh. If we are unable to build it dynamically for KitDLL, fall back to statically.

rkeene added on 2010-10-06 16:47:56:
Fixed in [76ec61a413]. The STATICMK4 option lets the user specify whether to build MK4 statically or dynamically. The default is statically, unless you are building KitDLL then it defaults to dynamically, failing that it uses static.