Overview
| Artifact ID: | b263437809dd8e827624e4667abbc3ead89548c1 |
|---|---|
| Ticket: | ff1065968a01e239f5e5a882a3ec4c9423918b8d
KitDLL needs to support static linking to Mk4tcl |
| User & Date: | rkeene on 2010-10-05 04:30:29 |
Changes
- comment changed to:
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.
- foundin changed to: "0.5.0"
- private_contact changed to: "346ea4e97beda2eb92a9ebba810f853dd2035948"
- severity changed to: "Important"
- status changed to: "Open"
- title changed to: "KitDLL needs to support static linking to Mk4tcl"
- type changed to: "Code Defect"