You should have an set up Tcl version greater or similar to 8.2 for many packages in Tcllib; for 64-little bit techniques, a latest Tcl 8.4 or newer is certainly suggested. The minimal version for all Tcllib deals is usually 8.0, credited to the use of namespaces.
Obtaining Tcllib If you put on't already possess Tcllib downloaded then discover for some ways to get to a functioning tcllib on your OS. Installing Tcllib If you used something like ActivéStates Distro, a deb or rpm package, you most likely don't want this. The least complicated method to install tcllib will be the incorporated installer, try: tclsh installer.tcl or want installer.tcl It jumps up a GUI (if can be obtainable) which will help you through the set up. You can get info about valid command range switches for the installer by working: tclsh installer.tcl -help Examining if Tcllib functions Fireplace up your defauIt tcl interpreter.
Consider this (or to need any of the some other deals):% package require nmea If it functions and returns the version quantity of the came back package, you installed Tcllib properly. If it will not work, verify your autopath adjustable like this:% collection autopath It offers to include the parent directory site of the website directory into which you set up the packages, or the install directory site itself. If it will be lacking, you have to add it to yóur autopath in yóur scripts.% lappend autópath /route/to/tcllib/installdir Upgrading an existing installation How do you enhance the edition? Perform you consider the defaults the installer gives you or do you discover where the present version is certainly and substitute that?
You can gladly install several tcllib variations in parallel. All deals use edition amounts so if you don't use package need -specific in your scripts you obtain the most recent compatible edition automatically. Therefore if you have got for example an ActiveTcl install, you just take the installer defaults (run the instaIler with your tcIsh from ActiveTcl, só it selects up the right autopath) and instaIl in parallel.
lf you are usually worried about storage area you can just delete the older tcllib directory site and good examples from your installation. There may be some unforeseen and unwanted side results if a package variations adjustments from major edition (1.x to 2.x for illustration) showing an API switch. This happénd with thé md5 packagé, which is definitely offered as an 1.x and 2.x version.
If your code simply utilizes package require md5 you obtain the most recent version, which is definitely 2.x, which may split scripts anticipating the older 1.x API. Basic fix is certainly to modify the package need to package réquire md5 1. Tcllibc tcllib ships with a module known as tcllibc, which will be compiles to a provided item. To compiIe it: tclsh sák.tcl critcl Thére can be currently no supply to automate set up, so installing is definitely a matter of replicating the material of segments/tcllibc to sométhing like /lib/tcIlibc.
Conversations Can anyone deal with why 64 little bit systems require a newer Tcl? Is usually it because Tcl itself provides difficulties before 8.4 on 64 bit machines? As considerably as i remember there are usually some packages like MD5 etc., which put on't function properly on 64-bit systems with a pré-8.4 Tcl, but i put on't rememeber the information, must become in the bugtrackér. 2006-10-05: Wierd on OSX the defaults are type of strange. It arrives up with /Program/Libray/bin tó install any executabIes? That should defauIt to somewhere on the /usr route (preferably /usr/local/bin).
I think I will possess to discover where tcllib1.8 is certainly hiding. Make sure you file a insect statement, when the installer will something strange. Class Installer.