diff options
Diffstat (limited to 'macosx/README')
| -rw-r--r-- | macosx/README | 356 |
1 files changed, 238 insertions, 118 deletions
diff --git a/macosx/README b/macosx/README index 578a2a9..8bd33d4 100644 --- a/macosx/README +++ b/macosx/README @@ -3,7 +3,6 @@ Tcl/Tk Mac OS X README This is the README file for the Mac OS X/Darwin version of Tcl/Tk. - 1. Where to go for support -------------------------- @@ -17,16 +16,11 @@ before asking on the list, many questions have already been answered). http://groups.google.com/group/comp.lang.tcl/ - The Tcl'ers Wiki also has many pages dealing with Tcl & Tk on Mac OS X, see - http://wiki.tcl.tk/references/3753! - http://wiki.tcl.tk/references/8361! + http://wiki.tcl.tk/_/ref?N=3753 + http://wiki.tcl.tk/_/ref?N=8361 - Please report bugs with Tcl or Tk on Mac OS X to the sourceforge bug trackers: - Tcl: http://sf.net/tracker/?func=add&group_id=10894&atid=110894 - Tk: http://sf.net/tracker/?func=add&group_id=12997&atid=112997 -please make sure that your report Tk specific bugs to the tktoolkit project bug -tracker rather than the tcl project bug tracker. -Mac OS X specific bugs should usually be assigned to 'das' or 'wolfsuit'. - + http://tcl.sourceforge.net/ 2. Using Tcl/Tk on Mac OS X --------------------------- @@ -34,12 +28,11 @@ Mac OS X specific bugs should usually be assigned to 'das' or 'wolfsuit'. - There are two versions of Tk available on Mac OS X: TkAqua using the native aqua widgets and look&feel, and TkX11 using the traditional unix X11 wigets. TkX11 requires an X11 server to be installed, such as Apple's X11 (which is -available as an optional install on recent Mac OS X retail disks). +available as an optional or default install on recent Mac OS X). TkAqua and TkX11 can be distinguished at runtime via [tk windowingsystem]. -- At a minimum, Mac OS X 10.1 is required to run Tcl and TkX11, and OS X 10.2 is -required to run TkAqua. However OS X 10.3 or higher is recommended (certain -[file] operations behave incorrectly on earlier releases). +- At a minimum, Mac OS X 10.3 is required to run Tcl and TkX11. +TkAqua requires Mac OS X 10.5 or later (starting with the Cocoa-based Tk 8.5.7). - Unless weak-linking is used, Tcl/Tk built on Mac OS X 10.x will not run on 10.y with y < x; on the other hand Tcl/Tk built on 10.y will always run on 10.x @@ -58,36 +51,36 @@ brings up the Tk console window at startup. This is the case when double clicking Wish in the Finder (or using 'open Wish.app' from the Terminal). - Tcl extensions can be installed in any of: - $HOME/Library/Tcl /Library/Tcl /Network/Library/Tcl /System/Library/Tcl - $HOME/Library/Frameworks /Library/Frameworks /Network/Library/Frameworks - /System/Library/Frameworks (searched in that order). + $HOME/Library/Tcl /Library/Tcl /System/Library/Tcl + $HOME/Library/Frameworks /Library/Frameworks /System/Library/Frameworks + (searched in that order). Given a potential package directory $pkg, Tcl on OSX checks for the file $pkg/Resources/Scripts/pkgIndex.tcl as well as the usual $pkg/pkgIndex.tcl. This allows building extensions as frameworks with all script files contained in the Resources/Scripts directory of the framework. - [load]able binary extensions can linked as either ordinary shared libraries -(.dylib) or as MachO bundles (since 8.4.10/8.5a3); only bundles can be unloaded, -and bundles are also loaded more efficiently from VFS (no temporary copy to the -native filesystem required). +(.dylib) or as MachO bundles (since 8.4.10/8.5a3); bundles have the advantage +that they are [load]ed more efficiently from a tcl VFS (no temporary copy to the +native filesystem required), and prior to Mac OS X 10.5, only bundles can be +[unload]ed. - The 'deploy' target of macosx/GNUmakefile installs the html manpages into the standard documentation location in the Tcl/Tk frameworks: Tcl.framework/Resources/Documentation/Reference/Tcl Tk.framework/Resources/Documentation/Reference/Tk -No nroff manpages are installed by default by the GNUmakefiles. +No nroff manpages are installed by default by the GNUmakefile. - The Tcl and Tk frameworks can be installed in any of the system's standard framework directories: - $HOME/Library/Frameworks /Library/Frameworks - /Network/Library/Frameworks /System/Library/Frameworks + $HOME/Library/Frameworks /Library/Frameworks /System/Library/Frameworks -- /usr/bin/wish8.x is a script that calls a copy of 'Wish' contained in +- ${prefix}/bin/wish8.x is a script that calls a copy of 'Wish' contained in Tk.framework/Resources -- if 'Wish' is started from the Finder or via 'open', $argv contains a -"-psn_XXXX" argument. This is the Wish's carbon process serial number, you may -need to filter it out for cross platform compatibility of your scripts. +- if 'Wish' is started from the Finder or via 'open', $argv may contain a +"-psn_XXXX" argument. This is the process serial number, you may need to filter +it out for cross platform compatibility of your scripts. - the env array is different when Wish is started from the Finder (i.e. via LaunchServices) than when it (or tclsh) is invoked from the Terminal, in @@ -95,56 +88,154 @@ particular PATH may not be what you expect. (Wish started by LaunchServices inherits loginwindow's environment variables, which are essentially those set in $HOME/.MacOSX/environment.plist, and are unrelated to those set in your shell). -- As of Tk 8.4.7, TkAqua has a version of the low-level drawing primitives using -the CoreGraphics routines - the code is primarily due to James Tittle. There -were numerous problems with the QD version, mostly due to the different drawing -model of QD & Tk. CG also trivially supports dashed lines, and the various end -caps & miters. The old QD code is retained for now, just in case there are any -compatibility problems. To switch back to the QD drawing, put - set tk::mac::useCGDrawing 0 -in your script before you do drawing. -All CG drawing is antialiased by default, but (outline) linewidth can be used to -control whether a line/shape is drawn antialiased. The antialiasing threshold is -0 by default (i.e. antialias everything), it can be changed by setting +- TkAqua drawing is antialiased by default, but (outline) linewidth can be used +to control whether a line/shape is drawn antialiased. The antialiasing threshold +is 0 by default (i.e. antialias everything), it can be changed by setting set tk::mac::CGAntialiasLimit <limit> in your script before drawing, in which case lines (or shapes with outlines) thinner than <limit> pixels will not be antialiased. -- Quickdraw text antialiasing is enabled by default when available (from 10.1.5 -onwards). Changing the global boolean variable '::tk::mac::antialiasedtext' -allows to dis/enable antialiasing on the fly from Tcl (even for existing text). +- Text antialiasing by default uses the standard OS antialising settings. +Setting the global variable '::tk::mac::antialiasedtext' allows to control text +antialiasing from Tcl: a value of 1 enables AA, 0 disables AA and -1 restores +the default behaviour of respecting the OS settings. - Scrollbars: There are two scrollbar variants in Aqua, normal & small. The -normal scrollbar has a small dimension of 15, the small variant 11. Access to -the small variant was added in Tk 8.4.2. - -- Cursors: You can now put up and spin the Classic MacOS spinner, and the -counting hands and watch cursor. The way this is done is each of the spinners -have a base name: - spinning: The circular B&W circular spinner - countinguphand: The counting up hand - countingdownhand: The counting down hand - countingupanddownhand: The counting up then down hand - watch: The watch cursor -Then to get the sequential variants, add an integer to the end of the base name. -So, for instance this code will spin the spinner: - proc spinCursor {widget count} { - $widget configure -cursor spinning$count - after 100 spinCursor [incr count] - } -This was added in Tk 8.4.2 +normal scrollbar has a small dimension of 15, the small variant 11. +Access to the small variant was added in Tk 8.4.2. + +- The default metrics of native buttons, radiobuttons, checkboxes and +menubuttons in the Cocoa-based Tk 8.5.7 and later preserve compatibility with +the older Carbon-based implementation, you can turn off the compatibility +metrics to get more native-looking spacing by setting: + set tk::mac::useCompatibilityMetrics 0 + +- TkAqua provides access to native OS X images via the Tk native bitmap facility +(including any image file readable by NSImage). A native bitmap name is +interpreted as follows (in order): + - predefined builtin 32x32 icon name (stop, caution, document, etc) + - name defined by [tk::mac::iconBitmap] + - NSImage named image name + - NSImage url string + - 4-char OSType of IconServices icon +the syntax of [tk::mac::iconBitmap] is as follows: + tk::mac::iconBitmap name width height -kind value +where -kind is one of + -file icon of file at given path + -fileType icon of given file type + -osType icon of given 4-char OSType file type + -systemType icon for given IconServices 4-char OSType + -namedImage named NSImage for given name + -imageFile image at given path +This support was added with the Cocoa-based Tk 8.5.7. + +- TkAqua cursor names are interpred as follows (in order): + - standard or platform-specific Tk cursor name (c.f. cursors.n) + - @path to any image file readable by NSImage + - NSImage named image name +Support for the latter two was added with the Cocoa-based Tk 8.5.7. + +- The standard Tk dialog commands [tk_getOpenFile], [tk_chooseDirectory], +[tk_getSaveFile] and [tk_messageBox] all take an additional optional -command +parameter on TkAqua. If it is present, the given command prefix is evaluated at +the global level when the dialog closes, with the dialog command's result +appended (the dialog command itself returning an emtpy result). If the -parent +option is also present, the dialog is configured as a modeless (window-modal) +sheet attached to the parent window and the dialog command returns immediately. +Support for -command was added with the Cocoa-based Tk 8.5.7. + +- The TkAqua-specific [tk::mac::standardAboutPanel] command brings the standard +Cocoa about panel to the front, with all its information filled in from your +application bundle files (i.e. standard about panel with no options specified). +See Apple Technote TN2179 and the AppKit documentation for -[NSApplication +orderFrontStandardAboutPanelWithOptions:] for details on the Info.plist keys and +app bundle files used by the about panel. +This support was added with the Cocoa-based Tk 8.5.7. + +- TkAqua has three special menu names that give access to the standard +Application, Window and Help menus, see menu.n for details. +By default, the platform-specific standard Help menu item "YourApp Help" peforms +the default Cocoa action of showing the Help Book configured in the +application's Info.plist (or displaying an alert if no Help Book is set). This +action can be customized by defining a procedure named [tk::mac::ShowHelp], if +present, this procedure is invoked instead by the standard Help menu item. +Support for the Window menu and [tk::mac::ShowHelp] was added with the +Cocoa-based Tk 8.5.7. + +- The TkAqua-specific command [tk::unsupported::MacWindowStyle style] is used to +get and set Mac OS X-specific toplevel window class and attributes. Note that +the window class and many attributes have to be set before the window is first +mapped for the change to have any effect. +The command has the following syntax: + tk::unsupported::MacWindowStyle style window ?class? ?attributes? +The 2 argument form returns a list of the current class and attributes for the +given window. The 3 argument form sets the class for the given window using the +default attributes for that class. The 4 argument form sets the class and the +list of attributes for the given window. +Window class names: + document, modal, floating, utility, toolbar, simple, help, overlay +Window attribute names: + standardDocument, standardFloating, resizable, fullZoom, horizontalZoom, + verticalZoom, closeBox, collapseBox, toolbarButton, sideTitlebar, + noTitleBar, unifiedTitleAndToolbar, metal, hud, noShadow, doesNotCycle, + noActivates, hideOnSuspend, inWindowMenu, ignoreClicks, doesNotHide, + canJoinAllSpaces, moveToActiveSpace, nonActivating, black, dark, light, + gray, red, green, blue, cyan, yellow, magenta, orange, purple, + brown, clear, opacity + +Note that not all attributes are valid for all window classes. +Support for the 3 argument form was added with the Cocoa-based Tk 8.5.7, at the +same time support for some legacy Carbon-specific classes and attributes was +removed (they are still accepted by the command but no longer have any effect). + +The color window attributes (black, dark, red, etc.) and the "opacity" allow one to set the background and opacity of a textured ("metal") window. This allows a Tk window to implement a window without the dividing line between the titlebar and the rest of the window, or the "unified toolbar" effect, which is increasingly standard in Mac applications. An example: + +toplevel .f +tk::unsupported::MacWindowStyle style .f document {metal light opaque closeBox collapseBox resizable standardDocument } + +pack [label .f.f -bg #ababab -text "This is a textured window\nwith opacity and a gray background\nsimilar to other Mac applications"] -fill both -expand yes + +The color attributes correspond to system-defined NSColor constants (e.g., red is [NSColor redColor]. The "light" and "dark" attributes correspond to lightGrayColor and darkGrayColor, respectively (because of the way the attributes are parsed, using "lightgray" and "darkgray" would cause a conflict with the core "gray" attribute). + +Below are the corresponding hex and/or Tk-defined colors that can be used from Tk widgets to match the NSColor-based attributes: + +black #000000 +dark #545454 +light #ababab +white #ffffff +gray #7f7f7f +red #ff0000 +green #00ff00 +blue #0000ff +cyan #00ffff +yellow #ffff00 +magenta #ff00ff +orange #ff8000 +purple #800080 +brown #996633 +clear systemTransparent + +- The Cocoa-based TkAqua can be distinguished from the older Carbon-based +version via the [winfo server .] command, example output on Mac OS X 10.5.7: + Cocoa-based: CG409.3 Apple AppKit GC 949.46 Mac OS X 1057 + Carbon-based: QD10R30 Apple 1057 + +- If you want to use Remote Debugging with Xcode, you need to set the +environment variable XCNOSTDIN to 1 in the Executable editor for Wish. That will +cause us to force closing stdin & stdout. Otherwise, given how Xcode launches +Wish remotely, they will be left open and then Wish & gdb will fight for stdin. 3. Building Tcl/Tk on Mac OS X ------------------------------ -- At least Mac OS X 10.1 is required to build Tcl and TkX11 and OS X 10.2 is -required to build TkAqua. Apple's Developer Tools need to be installed (only the -most recent version matching your OS release is supported). The Developer Tools -installer is available on Mac OS X retail disks or is present in -/Applications/Installers on Macs that came with OS X preinstalled. The most -recent version can be downloaded from the ADC website http://connect.apple.com -(after you register for free ADC membership). +- At least Mac OS X 10.3 is required to build Tcl and TkX11, and Mac OS X 10.5 +is required to build TkAqua. +Apple's Xcode Developer Tools need to be installed (only the most recent version +matching your OS release is supported), the Xcode installer is available on Mac +OS X install media or may be present in /Applications/Installers on Macs that +came with OS X preinstalled. The most recent version can always be downloaded +from the ADC website http://connect.apple.com (free ADC membership required). - Tcl/Tk are most easily built as Mac OS X frameworks via GNUmakefile in tcl/macosx and tk/macosx (see below for details), but can also be built with the @@ -156,34 +247,64 @@ The Mac OS X specific configure flags are --enable-aqua, --enable-framework and select based notifier). Note that --enable-aqua is incompatible with --disable-corefoundation (for both Tcl and Tk configure). -- It is also possible to build with Apple's IDE via the tk/macosx/Wish.pbproj -project, this simply calls through to the tk/macosx/Makefile. It requires a -build of the tcl/macosx/Tcl.pbproj project. - -- To build universal binaries, set CFLAGS as follows: - export CFLAGS="-arch ppc -arch i386 \ - -isysroot /Developer/SDKs/MacOSX10.4u.sdk -mmacosx-version-min=10.4" -This requires Mac OS X 10.4 and Xcode 2.2 (_not_ Xcode 2.1) and will work on any -of the architectures (the -isysroot flag is only required on PowerPC Tiger). +- It is also possible to build with the Xcode IDE via the projects in +tk/macosx, take care to use the project matching your DevTools and OS version: + Tk.xcode: for Xcode 3.1 on 10.5 + Tk.xcodeproj: for Xcode 3.2 on 10.6 +These have the following targets: + Tk: calls through to tk/macosx/GNUMakefile, + requires a corresponding build of the Tcl + target of tcl/macosx/Tcl.xcode. + tktest: static build of TkAqua tktest for debugging. + tktest-X11: static build of TkX11 tktest for debugging. +The following build configurations are available: + Debug: debug build for the active architecture, + with Fix & Continue enabled. + Debug gcc42: use gcc 4.2 compiler. + Debug gcc42 nogc: disable Objective-C garbage collection. + Debug llvmgcc42: use llvm-gcc 4.2 compiler. + DebugNoFixAndContinue: disable Fix & Continue. + DebugUnthreaded: disable threading. + DebugNoCF: disable corefoundation (X11 only). + DebugNoCFUnthreaded: disable corefoundation an threading. + DebugMemCompile: enable memory and bytecode debugging. + DebugLeaks: define PURIFY. + DebugGCov: enable generation of gcov data files. + Debug64bit: configure with --enable-64bit (requires + building on a 64bit capable processor). + Release: release build for the active architecture. + ReleaseUniversal: 32/64-bit universal build. + ReleaseUniversal gcc42: use gcc 4.2 compiler. + ReleaseUniversal llvmgcc42: use llvm-gcc 4.2 compiler. + ReleaseUniversal10.5SDK: build against the 10.5 SDK (with 10.5 + deployment target). + Note that the non-SDK configurations have their deployment target set to + 10.5 (Tk.xcode) resp. 10.6 (Tk.xcodeproj). +The Xcode projects refer to the toplevel tcl and tk source directories via the +the TCL_SRCROOT and TK_SRCROOT user build settings, by default these are set to +the project-relative paths '../../tcl' and '../../tk', if your source +directories are named differently, e.g. '../../tcl8.5' and '../../tk8.5', you +need to manually change the TCL_SRCROOT and TK_SRCROOT settings by editing your +${USER}.pbxuser file (located inside the Tk.xcodeproj bundle directory) with a +text editor. + +- To build universal binaries outside of the Xcode IDE, set CFLAGS as follows: + export CFLAGS="-arch i386 -arch x86_64 -arch ppc" +This requires Mac OS X 10.4 and Xcode 2.4 (or Xcode 2.2 if -arch x86_64 is +omitted, but _not_ Xcode 2.1) and will work on any architecture (on PowerPC +Tiger you need to add "-isysroot /Developer/SDKs/MacOSX10.4u.sdk"). Note that configure requires CFLAGS to contain a least one architecture that can -be run on the build machine (i.e. ppc on PowerPC, ppc or i386 on Intel). -Universal builds of Tk TEA extensions are also possible with CFLAGS set as -above, they will be [load]able by universal as well as thin binaries of Tk. -Note that while Tcl can be built for 64-bit architectures, neither TkAqua nor -TkX11 can be built for 64-bit as the corresponding GUI libraries are not -available for 64bit at present. However, linking a universal 'ppc i386' Tk -binary against a universal 'ppc ppc64 i386 x86_64' Tcl binary works just fine. -The Tk configure script automatically removes the 64-bit -arch flags from CFLAGS -to facilitate universal building of both Tcl and Tk with the same CFLAGS; the -same happens with configure in Tk extensions based on TEA 3.5 or later. +be run on the build machine (i.e. ppc on G3/G4, ppc or ppc64 on G5, ppc or i386 +on Core and ppc, i386 or x86_64 on Core2/Xeon). +Universal builds of Tcl TEA extensions are also possible with CFLAGS set as +above, they will be [load]able by universal as well as thin binaries of Tcl. - To enable weak-linking, set the MACOSX_DEPLOYMENT_TARGET environment variable -to the minimal OS version (>= 10.2) the binaries should be able to run on, e.g: - export MACOSX_DEPLOYMENT_TARGET=10.2 -This requires Mac OS X 10.2 and gcc 3.1; if you have gcc 4 or later you can set -CFLAGS instead: - export CFLAGS="-mmacosx-version-min=10.2" -Support for weak-linking was added to the code for 8.4.14/8.5a5. +to the minimal OS version the binaries should be able to run on, e.g: + export MACOSX_DEPLOYMENT_TARGET=10.4 +This requires at least gcc 3.1; with gcc 4 or later, set/add to CFLAGS instead: + export CFLAGS="-mmacosx-version-min=10.4" +Support for weak-linking was added with 8.4.14/8.5a5. Detailed Instructions for building with macosx/GNUmakefile ---------------------------------------------------------- @@ -197,59 +318,58 @@ trees in a common parent directory. [ or you can pass an argument of BUILD_DIR=/somewhere to the tcl and tk make. ] - The following instructions assume the Tcl and Tk source trees are named -"tcl${ver}" and "tk${ver}", respectively, where ${ver} is a shell variable -containing the Tcl and Tk version number (for example '8.4.12'). -Setup the shell variable as follows: - set ver="8.4.12" ;: if your shell is csh - ver="8.4.12" ;: if your shell is sh -The source trees will be named this way only if you are building from a release -archive, if you are building from CVS, the version numbers will be missing; so -set ${ver} to the empty string instead: - set ver="" ;: if your shell is csh - ver="" ;: if your shell is sh - -- The following steps will build Tcl and Tk from the Terminal, assuming you are -located in the directory containing the tcl and tk source trees: +"tcl${ver}" and "tk${ver}" (where ${ver} is a shell variable containing the +Tcl/Tk version number, e.g. '8.5'). +Setup this shell variable as follows: + ver="8.5" +If you are building from CVS, omit this step (CVS source tree names usually do +not contain a version number). + +- Setup environment variables as desired, e.g. for a universal build on 10.5: + CFLAGS="-arch i386 -arch x86_64 -arch ppc -mmacosx-version-min=10.5" + export CFLAGS + +- Change to the directory containing the Tcl and Tk source trees and build: make -C tcl${ver}/macosx make -C tk${ver}/macosx -and the following will then install Tcl and Tk onto the root volume (admin -password required): + +- Install Tcl and Tk onto the root volume (admin password required): sudo make -C tcl${ver}/macosx install sudo make -C tk${ver}/macosx install -if you don't have the admin password, you can install into your home directory, +if you don't have an admin password, you can install into your home directory instead by passing an INSTALL_ROOT argument to make: make -C tcl${ver}/macosx install INSTALL_ROOT="${HOME}/" make -C tk${ver}/macosx install INSTALL_ROOT="${HOME}/" -- The default Makefile targets will build _both_ debug and optimized versions of -the Tcl and Tk frameworks with the standard convention of naming the debug +- The default GNUmakefile targets will build _both_ debug and optimized versions +of the Tcl and Tk frameworks with the standard convention of naming the debug library Tcl.framework/Tcl_debug resp. Tk.framework/Tk_debug. This allows switching to the debug libraries at runtime by setting export DYLD_IMAGE_SUFFIX=_debug (c.f. man dyld for more details) If you only want to build and install the debug or optimized build, use the -'develop' or 'deploy' target variants of the Makefiles, respectively. +'develop' or 'deploy' target variants of the GNUmakefile, respectively. For example, to build and install only the optimized versions: make -C tcl${ver}/macosx deploy make -C tk${ver}/macosx deploy sudo make -C tcl${ver}/macosx install-deploy sudo make -C tk${ver}/macosx install-deploy -- The Makefiles can also build a version of 'Wish' that has the Tcl and Tk +- The GNUmakefile can also build a version of Wish.app that has the Tcl and Tk frameworks embedded in its application package. This allows for standalone deployment of the application with no installation required, e.g. from read-only -media. To build & install in this manner, use the 'embedded' target variants of -the Makefiles. For example, to build a standalone 'Wish.app' -in ./embedded/Applications/Utilities: +media. To build & install in this manner, use the 'embedded' variants of +the GNUmakefile targets. +For example, to build a standalone 'Wish.app' in ./emb/Applications/Utilities: make -C tcl${ver}/macosx embedded make -C tk${ver}/macosx embedded - sudo make -C tcl${ver}/macosx install-embedded INSTALL_ROOT=`pwd`/embedded/ - sudo make -C tk${ver}/macosx install-embedded INSTALL_ROOT=`pwd`/embedded/ + sudo make -C tcl${ver}/macosx install-embedded INSTALL_ROOT=`pwd`/emb/ + sudo make -C tk${ver}/macosx install-embedded INSTALL_ROOT=`pwd`/emb/ Notes: * if you've already built standard TclTkAqua, building embedded does not require any new compiling or linking, so you can skip the first two makes. - (making relinking unnecessary was added in 8.4.2) + (making relinking unnecessary was added with 8.4.2) * the embedded frameworks include only optimized builds and no documentation. * the standalone Wish has the directory Wish.app/Contents/lib in its auto_path. Thus you can place tcl extensions in this directory (i.e. embed @@ -260,9 +380,9 @@ still need a tcl sourcetree in the location specified in TCL_SRC_DIR in Tcl.framework/tclConfig.sh. Also, linking with Tcl.framework has to work exactly as indicated in TCL_LIB_SPEC in Tcl.framework/tclConfig.sh. If you used non-default install locations for Tcl.framework, specify them as -make overrides to the tk/macosx Makefile, e.g. +make overrides to the tk/macosx GNUmakefile, e.g. make -C tk${ver}/macosx \ TCL_FRAMEWORK_DIR=$HOME/Library/Frameworks TCLSH_DIR=$HOME/usr/bin sudo make -C tk${ver}/macosx install \ TCL_FRAMEWORK_DIR=$HOME/Library/Frameworks TCLSH_DIR=$HOME/usr/bin -The Makefile variables TCL_FRAMEWORK_DIR and TCLSH_DIR were added in Tk 8.4.3. +The Makefile variables TCL_FRAMEWORK_DIR and TCLSH_DIR were added with Tk 8.4.3. |