|
2010-10-06
| ||
| 16:47 | • Closed ticket [ff1065968a]: KitDLL needs to support static linking to Mk4tcl plus 2 other changes artifact: 6aa39ca867 user: rkeene | |
|
2010-10-05
| ||
| 04:33 | • Ticket [ff1065968a]: 1 change artifact: e41de65576 user: rkeene | |
| 04:30 | • Verified ticket [ff1065968a]. artifact: ba4d4a65d4 user: rkeene | |
| 04:30 | • New ticket [ff1065968a]. artifact: b263437809 user: rkeene | |
| Ticket Hash: | 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 | |||
| Description: | ||||
|
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: | ||||