From: Rupert B. <rb...@ma...> - 2001-12-04 18:05:53
|
Hi, With Apple's help, Jim has done a great job of bundling Tk on MacOSX in the form of a TK.framework. I would like to add the following requirements (for Tcl and Tk), which seem to span across several other frameworks on MacOSX (e.g. OpenGL et al., i.e. GL, AGL, GLUT, ...) : - in Tk.framework/Versions/<M>.<m>, I would like to : ln -s . lib ln -s Headers include ln -s Tk libtk.dylib ln -s Tk libtk.<M>.<m>.dylib (BTW, I always use the precise version number in my -F link option, never the 'Current' default : e.g. -F ...Tk.framework/Versions/8.4, not -F ...Tk.framework) - in Tk.framework, we might like to add the same thing, for those who link against the 'Current' version : ln -s . lib ln -s Headers include ln -s Tk libtk.dylib ln -s Tk libtk.<M>.<m>.dylib - in Tk.framework/Versions/<M>.<m>/Headers, to make the framework usable, I have had to symlink in all the contents of PrivateHeaders : for i in ../PrivateHeaders; do ln -s $i; done I think this 'PrivateHeaders' business is pretty useless, and the Apple documentation is not clear on what should go in there. So either symlink as I have, or put everything in Headers (I prefer the symlink solution, because it clearly shows which headers are the public interface). All this symlink-ing makes it easier to configure&build other stuff which uses Tcl or Tk without having to think too much. BTW [OT], it would be nice to be able to use something like the "--enable-framework" configure option to tell this thing's libtool to link to (for example) the Tk framework and not the Tk *.dylib, and generate a -F...Tk.framework/Versions/8.4 Tk link option instead of -L...Tk.framework/lib -ltk8.4 - I like the Tcl and Tk ProjectBuilder projects, although they are different. There is a problem in Tcl's : you cannot 'make clean' with the broom ! In Tk's, Jim worked nicely around some *glaring* bugs in Apple's "copy files build phase" : well done, I will reuse that. TTFN, Rupert |