home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.tcl
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!wupost!psuvax1!schwartz
- From: schwartz@roke.cs.psu.edu (Scott Schwartz)
- Subject: Re: Installing TCL/TK so it can be used for development
- Message-ID: <Brv0Cn.5F@cs.psu.edu>
- Sender: news@cs.psu.edu (Usenet)
- Nntp-Posting-Host: roke.cs.psu.edu
- References: <1992Jul21.000250.14233@twg.com> <ADRIANHO.92Jul21021938@barkley.berkeley.edu>
- <1992Jul23.124705.21577@NeoSoft.com>
- Date: Thu, 23 Jul 1992 21:45:06 GMT
- Lines: 13
-
-
- As long as we're comparing installation details, I've put tcl stuff in
- /depot/tcl/{bin,include,lib,library,man}
-
- I put the tk scripts in with the tcl ones, mostly since mxedit seemed
- to want it that way. Right now it seems like an acceptable choice,
- although I could see splitting them up if they grow in number by an
- appreciable amount.
-
- One problem with standard tcl is that TCL_LIBRARY is compiled in, so
- [info library] will be wrong if you move things around. Tclx does
- better, since things are set in a defaults file which you can
- override.
-