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.