History Of Ticket ff1065968a01e239f5e5a882a3ec4c9423918b8d

Artifacts Associated With Ticket ff1065968a01e239f5e5a882a3ec4c9423918b8d

  1. Ticket change [b263437809] (rid 811) by rkeene on 2010-10-05 04:30:29:

    1. comment initialized 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.
    2. foundin initialized to: "0.5.0"
    3. private_contact initialized to: "346ea4e97beda2eb92a9ebba810f853dd2035948"
    4. severity initialized to: "Important"
    5. status initialized to: "Open"
    6. title initialized to: "KitDLL needs to support static linking to Mk4tcl"
    7. type initialized to: "Code Defect"
  2. Ticket change [ba4d4a65d4] (rid 812) by rkeene on 2010-10-05 04:30:54:

    1. priority changed to: "Medium"
    2. resolution changed to: "Open"
    3. status changed to: "Verified"
  3. Ticket change [e41de65576] (rid 813) by rkeene on 2010-10-05 04:33:04:

    1. subsystem changed to: "KitDLL (The libTclkit Core)"
  4. Ticket change [6aa39ca867] (rid 837) by rkeene on 2010-10-06 16:47:56:

    1. Appended to comment:
      <hr /><i>rkeene added on 2010-10-06 16:47:56:</i><br />
      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.
    2. resolution changed to: "Fixed"
    3. status changed to: "Closed"