head	1.27;
access;
symbols
	core-8-5-9:1.27
	core-8-5-8:1.27
	macosx-cocoa-merge:1.27
	macosx-cocoa-premerge:1.27
	macosx-carbon-freeze:1.27
	core-8-5-7:1.27
	core-8-5-6:1.27
	core-8-6-b1:1.27
	core-8-6-a3:1.27
	core-8-5-5:1.27
	core-8-6-a2:1.27
	core-8-5-4:1.27
	core-8-5-3:1.27
	core-8-6-a1:1.27
	core-8-4-19:1.19.2.3
	core-8-5-branch:1.27.0.2
	core-8-5-2:1.27
	core-8-4-18:1.19.2.3
	core-8-5-1:1.26
	core-8-4-17:1.19.2.3
	core-8-5-0:1.26
	core-8-5-b3:1.23
	core-8-5-b2:1.23
	core-8-4-16:1.19.2.3
	core-8-5-b1:1.23
	core-stablilizer-merge:1.22
	core-stabilizer-branch:1.22.0.2
	core-stabilizer-merge:1.27
	core-8-4-15:1.19.2.3
	core-8-5-a6:1.22
	core-8-5-a5:1.22
	core-8-4-14:1.19.2.2
	core-8-5-a4:1.22
	core-8-4-13:1.19.2.2
	core-8-4-12:1.19.2.2
	core-8-4-11:1.19
	core-8-5-a3:1.21
	core-8-4-10:1.19
	core-8-4-9-branch:1.19.0.4
	core-8-5-a2:1.21
	core-8-4-9:1.19
	core-8-4-8:1.19
	core-8-4-7:1.19
	core-8-5-a1:1.20
	core-8-4-6:1.19
	core-8-4-5:1.19
	mistachkin-dev-branch:1.20.0.2
	core-8-4-4:1.19
	core-8-4-3:1.19
	core-8-4-branch:1.19.0.2
	core-8-4-2:1.19
	core-8-4-1:1.18
	core-8-3-5:1.9.2.2
	core-8-4-0:1.16
	macosx-8-4-merge-2002-08-31-trunk:1.16
	macosx-8-4-premerge-2002-08-31-branch:1.12.2.2
	macosx-8-4-premerge-2002-08-31-trunk:1.16
	macosx-8-4-merge-2002-08-30-branch:1.12.2.2
	macosx-8-4-merge-2002-08-30-trunk:1.16
	macosx-8-4-merge-2002-08-20-branch:1.12.2.2
	macosx-8-4-merge-2002-08-20-trunk:1.16
	core-8-4-b2:1.16
	core-8-4-b1:1.15
	macosx-premerge-6-9-02:1.12
	core-8-4-a4:1.14
	core-8-3-4:1.9.2.1
	macosx-8-4-branch:1.12.0.2
	macosx-8-4-branchpoint:1.12
	core-8-4-a3:1.12
	core-8-3-3:1.9
	dgp-privates-into-namespace:1.11.0.4
	tclpro-1-5-0:1.9
	core-8-4-win-speedup:1.11.0.2
	core-8-4-a2:1.11
	tclpro-1-4-1:1.9
	tclpro-1-4-0:1.9
	core-8-3-2:1.9
	ajuba-ajuba2-2-1-base:1.9
	ajuba-ajuba2-2-0:1.9
	core-8-4-a1:1.10
	core-8-3-1-branch:1.9.0.2
	core-8-3-1:1.9
	scriptics-sc-2-0-b5:1.8
	scriptics-sc-2-0-fixed:1.8
	scriptics-sc-2-0-b2:1.8
	scriptics-sc-2-0-b1:1.8
	core-8-3-0:1.8
	core-8-3-b2:1.7
	core-8-3-b1:1.7
	scriptics-sc-1-1:1.6
	scriptics-sc-1-1-b1:1.6
	core-8-2-3:1.6
	scriptics-sc-1-1-branch:1.6.0.8
	scriptics-sc-1-1-base:1.6
	scriptics-sc-1-0:1.6
	scriptics-sc-1-0-branch:1.6.0.6
	scriptics-sc-1-0-base:1.6
	core-8-2-2:1.6
	core-8-2-1:1.6
	scriptics-bc-1-0-b1:1.6
	core-8-2-1-branch:1.6.0.4
	scriptics-tclpro-1-3-0:1.6
	core-8-2-0:1.6
	core-8-2-b3-branch:1.6.0.2
	core-8-2-b3-base:1.6
	scriptics-tclpro-1-3-b4:1.6
	core-8-2-b2:1.6
	scriptics-tclpro-1-3-b3:1.6
	core-8-2-b1:1.6
	scriptics-tclpro-1-3-b2:1.5
	merge-to-mainline-5/21/99:1.5
	scriptics-tclpro-1-3-b2-branch:1.5.0.2
	core-8-1-1:1.5
	scriptics-tclpro-1-3-b1:1.5
	core-8-1-1-base:1.5
	core-8-1-0:1.4.4.1
	merge-to-mainline-4-29-99:1.4.4.1
	merge-to-mainline-4-23-99:1.4.4.1
	core-8-1-branch-old:1.1.0.4
	core-8-0-6-branch:1.3.0.6
	core-8-0-6-base:1.3
	core-8-0-5:1.3
	core-8-1-b3:1.1.4.3
	core-8-1-b2:1.1.4.3
	dev-8-1-stubs-branch:1.1.4.3.0.2
	dev-stubs-branch:1.3.0.4
	scriptics-tclpro-1-2:1.3
	scriptics-tclpro-1-2-b2:1.3
	core-8-1-merge-2/10/99:1.3
	core-8-0-5-branch:1.3.0.2
	core-8-0-5-base:1.3
	scriptics-tclpro-1-2-b1:1.2
	scriptics-tclpro-1-2-a1:1.2
	core-8-1-b1:1.1.4.2
	core-8-0-4:1.2
	core-8-1-a2:1.1.4.1
	core-8-0-2:1.1
	core-8-0-3:1.2;
locks; strict;
comment	@# @;


1.27
date	2008.02.14.15.45.43;	author dkf;	state Exp;
branches;
next	1.26;

1.26
date	2007.12.13.15.28.49;	author dgp;	state Exp;
branches;
next	1.25;

1.25
date	2007.12.07.20.47.56;	author dgp;	state Exp;
branches;
next	1.24;

1.24
date	2007.11.23.16.41.06;	author dkf;	state Exp;
branches;
next	1.23;

1.23
date	2007.09.10.22.59.06;	author hobbs;	state Exp;
branches;
next	1.22;

1.22
date	2005.12.03.00.41.48;	author das;	state Exp;
branches
	1.22.2.1;
next	1.21;

1.21
date	2004.03.17.18.15.50;	author das;	state Exp;
branches;
next	1.20;

1.20
date	2003.03.04.23.50.44;	author dgp;	state Exp;
branches;
next	1.19;

1.19
date	2003.02.27.00.05.54;	author hobbs;	state Exp;
branches
	1.19.2.1;
next	1.18;

1.18
date	2002.10.10.05.01.23;	author hobbs;	state Exp;
branches;
next	1.17;

1.17
date	2002.09.27.18.09.53;	author dgp;	state Exp;
branches;
next	1.16;

1.16
date	2002.07.24.18.42.23;	author hobbs;	state Exp;
branches;
next	1.15;

1.15
date	2002.06.25.16.45.12;	author rmax;	state Exp;
branches;
next	1.14;

1.14
date	2002.03.05.20.34.15;	author hobbs;	state Exp;
branches;
next	1.13;

1.13
date	2002.03.04.23.31.45;	author hobbs;	state Exp;
branches;
next	1.12;

1.12
date	2001.07.05.17.23.53;	author hobbs;	state Exp;
branches
	1.12.2.1;
next	1.11;

1.11
date	2000.08.25.05.55.05;	author mo;	state Exp;
branches
	1.11.2.1
	1.11.4.1;
next	1.10;

1.10
date	2000.05.03.00.18.36;	author hobbs;	state Exp;
branches;
next	1.9;

1.9
date	2000.04.26.17.37.35;	author hobbs;	state Exp;
branches
	1.9.2.1;
next	1.8;

1.8
date	2000.02.10.08.53.15;	author hobbs;	state Exp;
branches;
next	1.7;

1.7
date	99.10.01.22.45.27;	author hobbs;	state Exp;
branches;
next	1.6;

1.6
date	99.06.25.23.30.26;	author welch;	state Exp;
branches;
next	1.5;

1.5
date	99.04.24.01.50.51;	author stanton;	state Exp;
branches;
next	1.4;

1.4
date	99.04.16.01.51.45;	author stanton;	state Exp;
branches
	1.4.4.1;
next	1.3;

1.3
date	99.02.09.03.46.27;	author stanton;	state Exp;
branches;
next	1.2;

1.2
date	98.09.14.18.23.54;	author stanton;	state Exp;
branches;
next	1.1;

1.1
date	98.04.01.09.59.32;	author rjohnson;	state Exp;
branches
	1.1.4.1;
next	;

1.1.4.1
date	98.09.29.00.25.59;	author stanton;	state Exp;
branches;
next	1.1.4.2;

1.1.4.2
date	98.09.30.02.19.10;	author stanton;	state Exp;
branches;
next	1.1.4.3;

1.1.4.3
date	99.02.11.04.13.49;	author stanton;	state Exp;
branches;
next	;

1.4.4.1
date	99.04.22.23.06.00;	author welch;	state Exp;
branches;
next	;

1.9.2.1
date	2001.10.03.22.04.52;	author hobbs;	state Exp;
branches;
next	1.9.2.2;

1.9.2.2
date	2002.10.16.01.05.57;	author hobbs;	state Exp;
branches;
next	;

1.11.2.1
date	2002.04.02.20.58.00;	author hobbs;	state Exp;
branches;
next	;

1.11.4.1
date	2001.07.05.19.14.13;	author dgp;	state Exp;
branches;
next	;

1.12.2.1
date	2002.06.10.05.38.26;	author wolfsuit;	state Exp;
branches;
next	1.12.2.2;

1.12.2.2
date	2002.08.20.20.27.16;	author das;	state Exp;
branches;
next	;

1.19.2.1
date	2005.12.02.21.13.39;	author dgp;	state Exp;
branches;
next	1.19.2.2;

1.19.2.2
date	2005.12.03.00.36.51;	author das;	state Exp;
branches;
next	1.19.2.3;

1.19.2.3
date	2007.05.25.16.03.37;	author dgp;	state Exp;
branches;
next	;

1.22.2.1
date	2007.09.11.18.32.36;	author dgp;	state Exp;
branches;
next	1.22.2.2;

1.22.2.2
date	2007.11.25.06.47.34;	author dgp;	state Exp;
branches;
next	1.22.2.3;

1.22.2.3
date	2007.12.10.18.39.31;	author dgp;	state Exp;
branches;
next	1.22.2.4;

1.22.2.4
date	2008.03.07.22.03.50;	author dgp;	state Exp;
branches;
next	;


desc
@@


1.27
log
@Document missing configure options.
@
text
@Tk UNIX README
--------------

This is the directory where you configure, compile, test, and install UNIX
versions of Tk. This directory also contains source files for Tk that are
specific to UNIX.

The information in this file is maintained at:
	http://www.tcl.tk/doc/howto/compile.html

For information on platforms where Tcl/Tk is known to compile, along with any
porting notes for getting it to work on those platforms, see:
	http://www.tcl.tk/software/tcltk/platforms.html

The rest of this file contains instructions on how to do this. The release
should compile and run either "out of the box" or with trivial changes on any
UNIX-like system that approximates POSIX, BSD, or System V. We know that it
runs on workstations from Sun, H-P, DEC, IBM, and SGI, as well as PCs running
Linux, BSDI, and SCO UNIX. To compile for a PC running Windows, see the README
file in the directory ../win. To compile for MacOSX, see the README file in
the directory ../macosx.

RCS: @@(#) $Id: README,v 1.26 2007/12/13 15:28:49 dgp Exp $

How To Compile And Install Tk:
------------------------------

(a) Make sure that the Tcl release is present in the directory
    ../../tcl<version> (or else use the "--with-tcl" switch described below).
    This release of Tk will only work with the equivalently versioned Tcl
    release. Also, be sure that you have configured Tcl before you configure
    Tk.

(b) Check for patches as described in ../README.

(c) If you have already compiled Tk once in this directory and are now
    preparing to compile again in the same directory but for a different
    platform, or if you have applied patches, type "make distclean" to discard
    all the configuration information computed previously.

(d) Type "./configure". This runs a configuration script created by GNU
    autoconf, which configures Tk for your system and creates a Makefile. The
    configure script allows you to customize the Tk configuration for your
    site; for details on how you can do this, type "./configure -help" or
    refer to the autoconf documentation (not included here). Tk's "configure"
    script supports the following special switches in addition to the standard
    ones:

	--with-tcl=DIR		Specifies the directory containing the Tcl
				binaries and Tcl's platform-dependent
				configuration information. By default the Tcl
				directory is assumed to be in the location
				given by (a) above.
	--with-x=DIR		Tells configure where to find an installation
				of the X Window System. Not normally needed.
	--enable-threads	If this switch is set, Tk will compile itself
				with multithreading support.
	--enable-shared		If this switch is specified, Tk will compile
				itself as a shared library if it can figure
				out how to do that on this platform. This is
				the default on platforms where we know how to
				build shared libraries.
	--disable-shared	If this switch is specified, Tk will compile
				itself as a static library.
	--disable-rpath		Turns off use of the rpath link option on
				platforms that would otherwise use it.
	--enable-symbols	Build with debugging symbols. By default
				standard debugging symbols are used. You can
				specify the value "mem" to include
				TCL_MEM_DEBUG memory debugging.
	--disable-symbols	Build without debugging symbols
	--enable-64bit		Enable 64bit support (where applicable)
	--disable-64bit		Disable 64bit support (where applicable)
	--enable-64bit-vis	Enable 64bit Sparc VIS support
	--disable-64bit-vis	Disable 64bit Sparc VIS support
	--disable-xft		Disable support for antialiased fonts via the
				Freetype/xft library. By default, this is
				switched on whenever the configure script can
				detect the required libraries.
	--enable-man-symlinks	Use symlinks for linking the manpages that
				should be reachable under several names.
	--enable-man-compression=PROG
				Compress the manpages using PROG.
	--enable-man-suffix=STRING
				Add STRING to the name of each of the manual
				pages. If specified without giving STRING, the
				suffix will be "tk".

    Mac OS X only:

	--enable-framework	Package Tk as a framework.
	--disable-corefoundation Disable use of CoreFoundation API.
	--enable-aqua		Use Aqua windowingsystem rather than X11,
				requires --enable-corefoundation with Tcl and
				Tk.

    Note: by default gcc will be used if it can be located on the PATH. If you
    want to use cc instead of gcc, set the CC environment variable to "cc"
    before running configure. It is not safe to change the Makefile to use gcc
    after configure is run.

    Note: be sure to use only absolute path names (those starting with "/") in
    the --prefix and --exec-prefix options.

(e) Type "make". This will create a library archive called "libtk<version>.a"
    or "libtk<version>.so" and an interpreter application called "wish" that
    allows you to type Tcl/Tk commands interactively or execute script files.
    It will also create a stub library archive "libtkstub<version>.a" that
    developers may link against other C code to produce loadable extensions
    that call into Tk's public interface routines.

(f) If the make fails then you'll have to personalize the Makefile for your
    site or possibly modify the distribution in other ways. First check the
    porting Web page above to see if there are hints for compiling on your
    system. If you need to modify Makefile, there are comments at the
    beginning of it that describe the things you might want to change and how
    to change them.

(g) Type "make install" to install Tk's binaries and script files in standard
    places. You'll need write permission on the installation directories to do
    this. The installation directories are determined by the "configure"
    script and may be specified with the --prefix and --exec-prefix options to
    "configure". See the Makefile for information on what directories were
    chosen. You should not override these choices by modifying the Makefile,
    or by copying files post-install. The installed binaries have embedded
    within them path values relative to the install directory. If you change
    your mind about where Tk should be installed, start this procedure over
    again from step (a) so that the path embedded in the binaries agrees with
    the install location.

(h) At this point you can play with Tk by running the installed "wish"
    executable, or via the "make shell" target, and typing Tcl/Tk commands at
    the interactive prompt.

If you have trouble compiling Tk, see the URL noted above about working
platforms. It contains information that people have provided about changes
they had to make to compile Tk in various environments. We're also interested
in hearing how to change the configuration setup so that Tk compiles on
additional platforms "out of the box".

Note: Do not specify either of the TCL_LIBRARY and TK_LIBRARY environment
variables in a production installation, as this can cause conflicts between
different versions of the libraries. Instead, the libraries should have the
correct locations of their associated script directories built into them.

Test suite
----------

Tk has a substantial self-test suite, consisting of a set of scripts in the
subdirectory "tests". To run the test suite just type "make test" in this
directory. You should then see a printout of the test files processed. If any
errors occur, you'll see a much more substantial printout for each error. In
order to avoid false error reports, be sure to run the tests with an empty
resource database (e.g., remove your .Xdefaults file or delete any entries
starting with *). Also, don't try to do anything else with your display or
keyboard while the tests are running, or you may get false violations. See the
README file in the "tests" directory for more information on the test suite.

If the test suite generates errors, most likely they are due to non-portable
tests that are interacting badly with your system configuration. We are
gradually eliminating the non-portable tests, but this release includes many
new tests so there will probably be some portability problems. As long as the
test suite doesn't core dump, it's probably safe to conclude that any errors
represent portability problems in the test suite and not fundamental flaws
with Tk.

There are also a number of visual tests for things such as screen layout,
Postscript generation, etc. These tests all have to be run by manually
enabling the "userInteraction" constraint when testing, and the results have
to be verified visually. This can be done with:

    make test TESTFLAGS="-constraints userInteraction"

Some tests will present a main window with a bunch of menus, which you can use
to select various tests.
@


1.26
log
@merge stable branch onto HEAD
@
text
@d4 3
a6 3
This is the directory where you configure, compile, test, and install
UNIX versions of Tk.  This directory also contains source files for Tk
that are specific to UNIX.
d11 2
a12 2
For information on platforms where Tcl/Tk is known to compile, along
with any porting notes for getting it to work on those platforms, see:
d15 7
a21 7
The rest of this file contains instructions on how to do this.  The
release should compile and run either "out of the box" or with trivial
changes on any UNIX-like system that approximates POSIX, BSD, or System
V.  We know that it runs on workstations from Sun, H-P, DEC, IBM, and
SGI, as well as PCs running Linux, BSDI, and SCO UNIX.  To compile for
a PC running Windows, see the README file in the directory ../win.  To
compile for MacOSX, see the README file in the directory ../macosx.
d23 1
a23 1
RCS: @@(#) $Id: README,v 1.22.2.3 2007/12/10 18:39:31 dgp Exp $
d29 4
a32 4
    ../../tcl<version> (or else use the "--with-tcl" switch described
    below).  This release of Tk will only work with the equivalently
    versioned Tcl release. Also, be sure that you have configured Tcl before
    you configure Tk.
d38 10
a47 2
    platform, or if you have applied patches, type "make distclean" to
    discard all the configuration information computed previously.
a48 7
(d) Type "./configure".  This runs a configuration script created by GNU
    autoconf, which configures Tk for your system and creates a Makefile.
    The configure script allows you to customize the Tk configuration for
    your site; for details on how you can do this, type "./configure
    -help" or refer to the autoconf documentation (not included here).
    Tk's "configure" script supports the following special switches in
    addition to the standard ones:
d51 7
a57 5
				configuration information.  By default
				the Tcl directory is assumed to be in the
				location given by (a) above.
	--enable-threads	If this switch is set, Tk will compile
				itself with multithreading support.
d60 3
a62 3
				out how to do that on this platform.  This
				is the default on platforms where we know
				how to build shared libraries.
d65 5
a69 3
	--enable-symbols	Build with debugging symbols  By default
				standard debugging symbols are used.  You
				can specify the value "mem" to include
a71 5
	--disable-xft		Disable support for antialiased fonts via
				the Freetype/xft library. By default,
				this is switched on whenever the
				configure script can detect the required
				libraries.
d76 4
d85 4
a88 3
				Add STRING to the name of each of the
				manual pages. If specified without giving
				STRING, the suffix will be "tk".
d90 1
d94 2
a95 2
				requires --enable-corefoundation with Tcl
				and Tk.
d97 33
a129 34
    Note: by default gcc will be used if it can be located on the PATH.
    if you want to use cc instead of gcc, set the CC environment variable
    to "cc" before running configure. It is not safe to change the Makefile
    to use gcc after configure is run.

    Note: be sure to use only absolute path names (those starting with "/")
    in the --prefix and --exec-prefix options.

(e) Type "make".  This will create a library archive called
    "libtk<version>.a" or "libtk<version>.so" and an interpreter
    application called "wish" that allows you to type Tcl/Tk commands
    interactively or execute script files.  It will also create a
    stub library archive "libtkstub<version>.a" that developers may
    link against other C code to produce loadable extensions that call
    into Tk's public interface routines.

(f) If the make fails then you'll have to personalize the Makefile
    for your site or possibly modify the distribution in other ways.
    First check the porting Web page above to see if there are hints
    for compiling on your system.  If you need to modify Makefile,
    there are comments at the beginning of it that describe the things
    you might want to change and how to change them.

(g) Type "make install" to install Tk's binaries and script files in
    standard places.  You'll need write permission on the installation
    directories to do this.  The installation directories are
    determined by the "configure" script and may be specified with
    the --prefix and --exec-prefix options to "configure".  See the
    Makefile for information on what directories were chosen.  You
    should not override these choices by modifying the Makefile, or by
    copying files post-install.  The installed binaries have embedded within
    them path values relative to the install directory.  If you change your
    mind about where Tk should be installed, start this procedure over again        from step (a) so that the path embedded in the binaries agrees with the
    install location.
d132 2
a133 2
    executable, or via the "make shell" target, and typing Tcl/Tk commands
    at the interactive prompt.
d136 4
a139 4
platforms.  It contains information that people have provided about changes
they had to make to compile Tk in various environments.  We're also
interested in hearing how to change the configuration setup so that Tk
compiles on additional platforms "out of the box".
d142 3
a144 4
variables in a production installation, as this can cause conflicts
between different versions of the libraries. Instead, the libraries
should have the correct locations of their associated script directories
built into them.
d149 17
a165 18
Tk has a substantial self-test suite, consisting of a set of scripts in
the subdirectory "tests".  To run the test suite just type "make test"
in this directory.  You should then see a printout of the test files
processed.  If any errors occur, you'll see a much more substantial
printout for each error.  In order to avoid false error reports, be sure
to run the tests with an empty resource database (e.g., remove your
.Xdefaults file or delete any entries starting with *).  Also, don't
try to do anything else with your display or keyboard while the tests
are running, or you may get false violations.  See the README file in
the "tests" directory for more information on the test suite.

If the test suite generates errors, most likely they are due to non-
portable tests that are interacting badly with your system configuration.
We are gradually eliminating the non-portable tests, but this release
includes many new tests so there will probably be some portability
problems.  As long as the test suite doesn't core dump, it's probably
safe to conclude that any errors represent portability problems in the
test suite and not fundamental flaws with Tk.
d168 8
a175 6
Postscript generation, etc.  These tests all have to be run by manually
enabling the "userInteraction" constraint when testing, and the results
have to be verified visually..  This can be done with
     make test TESTFLAGS="-constraints userInteraction"
Some tests will present a main window with a bunch of menus, which you can
use to select various tests.
@


1.25
log
@        * unix/README:  Mention the stub library created by `make` and warn
        about the effect of embedded paths in the installed binaries.
        Thanks to Larry Virden.  [Tcl Bug 1794084]
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.24 2007/11/23 16:41:06 dkf Exp $
@


1.24
log
@General improvements to Unix README
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.23 2007/09/10 22:59:06 hobbs Exp $
d102 4
a105 1
    interactively or execute script files.
d119 10
a128 16
    Makefile for information on what directories were chosen; you
    can override these choices by modifying the "prefix" and
    "exec_prefix" variables in the Makefile.

(h) At this point you can play with Tk by invoking the "wish"
    program and typing Tcl/Tk commands.  However, if you haven't installed
    Tk then you'll first need to set your TK_LIBRARY environment
    variable to hold the full path name of the "library" subdirectory.
    If you haven't installed Tcl either then you'll need to set your
    TCL_LIBRARY environment variable as well (see the Tcl README file
    for information on this).  Note that installed versions of wish,
    libtk.a, libtk.so, and the Tk library have a version number in their
    names, such as "wish8.5" or "libtk8.5.so"; to use the installed
    versions, either specify the version number or create a symbolic
    link (e.g. from "wish" to "wish8.5"). You can also play with Tcl/Tk
    by typing "make shell", provided Tcl has been built first.
@


1.23
log
@typo corrections [Bug 1788682]
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.22 2005/12/03 00:41:48 das Exp $
d31 1
a31 1
    version Tcl release. Also, be sure that you have configured Tcl before
d42 6
a47 6
    autoconf, which configures Tcl for your system and creates a
    Makefile.  The configure script allows you to customize the Tcl
    configuration for your site; for details on how you can do this,
    type "./configure -help" or refer to the autoconf documentation (not
    included here).  Tk's "configure" script supports the following
    special switches in addition to the standard ones:
d53 1
a53 1
	--enable-threads	If this switch is set, Tcl will compile
d62 1
a62 1
	--enable-symbols	build with debugging symbols  By default
d66 10
a75 5
	--disable-symbols	build without debugging symbols
	--enable-64bit		enable 64bit support (where applicable)
	--disable-64bit		disable 64bit support (where applicable)
	--enable-64bit-vis	enable 64bit Sparc VIS support
	--disable-64bit-vis	disable 64bit Sparc VIS support
d80 10
a89 5
    Mac OS X only: 
	--enable-framework	package Tk as a framework.
	--disable-corefoundation disable use of CoreFoundation API.
	--enable-aqua		use Aqua windowingsystem rather than X11,
				requires --enable-corefoundation with tcl & tk.
d101 1
a101 1
    application called "wish" that allows you to type Tcl commands
d110 1
a110 1
    
d121 1
a121 1
    program and typing Tcl commands.  However, if you haven't installed
d130 2
a131 1
    link (e.g. from "wish" to "wish8.5").
d139 6
@


1.22
log
@documented macosx-only configure options.
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.21 2004/03/17 18:15:50 das Exp $
d103 1
a103 1
    directoryies to do this.  The installation directories are
d138 1
a138 1
try to do anything else with your display or keyboard whlie the tests
@


1.22.2.1
log
@merge updates from HEAD
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.22 2005/12/03 00:41:48 das Exp $
d103 1
a103 1
    directories to do this.  The installation directories are
d138 1
a138 1
try to do anything else with your display or keyboard while the tests
@


1.22.2.2
log
@merge updates from HEAD
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.22.2.1 2007/09/11 18:32:36 dgp Exp $
d31 1
a31 1
    versioned Tcl release. Also, be sure that you have configured Tcl before
d42 6
a47 6
    autoconf, which configures Tk for your system and creates a Makefile.
    The configure script allows you to customize the Tk configuration for
    your site; for details on how you can do this, type "./configure
    -help" or refer to the autoconf documentation (not included here).
    Tk's "configure" script supports the following special switches in
    addition to the standard ones:
d53 1
a53 1
	--enable-threads	If this switch is set, Tk will compile
d62 1
a62 1
	--enable-symbols	Build with debugging symbols  By default
d66 5
a70 10
	--disable-symbols	Build without debugging symbols
	--disable-xft		Disable support for antialiased fonts via
				the Freetype/xft library. By default,
				this is switched on whenever the
				configure script can detect the required
				libraries.
	--enable-64bit		Enable 64bit support (where applicable)
	--disable-64bit		Disable 64bit support (where applicable)
	--enable-64bit-vis	Enable 64bit Sparc VIS support
	--disable-64bit-vis	Disable 64bit Sparc VIS support
d75 5
a79 10
	--enable-man-suffix=STRING
				Add STRING to the name of each of the
				manual pages. If specified without giving
				STRING, the suffix will be "tk".
    Mac OS X only:
	--enable-framework	Package Tk as a framework.
	--disable-corefoundation Disable use of CoreFoundation API.
	--enable-aqua		Use Aqua windowingsystem rather than X11,
				requires --enable-corefoundation with Tcl
				and Tk.
d91 1
a91 1
    application called "wish" that allows you to type Tcl/Tk commands
d100 1
a100 1

d111 1
a111 1
    program and typing Tcl/Tk commands.  However, if you haven't installed
d120 1
a120 2
    link (e.g. from "wish" to "wish8.5"). You can also play with Tcl/Tk
    by typing "make shell", provided Tcl has been built first.
a127 6
Note: Do not specify either of the TCL_LIBRARY and TK_LIBRARY environment
variables in a production installation, as this can cause conflicts
between different versions of the libraries. Instead, the libraries
should have the correct locations of their associated script directories
built into them.

@


1.22.2.3
log
@merge updates from HEAD
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.22.2.2 2007/11/25 06:47:34 dgp Exp $
d102 1
a102 4
    interactively or execute script files.  It will also create a
    stub library archive "libtkstub<version>.a" that developers may
    link against other C code to produce loadable extensions that call
    into Tk's public interface routines.
d116 16
a131 10
    Makefile for information on what directories were chosen.  You
    should not override these choices by modifying the Makefile, or by
    copying files post-install.  The installed binaries have embedded within
    them path values relative to the install directory.  If you change your
    mind about where Tk should be installed, start this procedure over again        from step (a) so that the path embedded in the binaries agrees with the
    install location.

(h) At this point you can play with Tk by running the installed "wish"
    executable, or via the "make shell" target, and typing Tcl/Tk commands
    at the interactive prompt.
@


1.22.2.4
log
@merge updates from HEAD
@
text
@d4 3
a6 3
This is the directory where you configure, compile, test, and install UNIX
versions of Tk. This directory also contains source files for Tk that are
specific to UNIX.
d11 2
a12 2
For information on platforms where Tcl/Tk is known to compile, along with any
porting notes for getting it to work on those platforms, see:
d15 7
a21 7
The rest of this file contains instructions on how to do this. The release
should compile and run either "out of the box" or with trivial changes on any
UNIX-like system that approximates POSIX, BSD, or System V. We know that it
runs on workstations from Sun, H-P, DEC, IBM, and SGI, as well as PCs running
Linux, BSDI, and SCO UNIX. To compile for a PC running Windows, see the README
file in the directory ../win. To compile for MacOSX, see the README file in
the directory ../macosx.
d23 1
a23 1
RCS: @@(#) $Id: README,v 1.22.2.3 2007/12/10 18:39:31 dgp Exp $
d29 4
a32 4
    ../../tcl<version> (or else use the "--with-tcl" switch described below).
    This release of Tk will only work with the equivalently versioned Tcl
    release. Also, be sure that you have configured Tcl before you configure
    Tk.
d38 2
a39 10
    platform, or if you have applied patches, type "make distclean" to discard
    all the configuration information computed previously.

(d) Type "./configure". This runs a configuration script created by GNU
    autoconf, which configures Tk for your system and creates a Makefile. The
    configure script allows you to customize the Tk configuration for your
    site; for details on how you can do this, type "./configure -help" or
    refer to the autoconf documentation (not included here). Tk's "configure"
    script supports the following special switches in addition to the standard
    ones:
d41 7
d50 5
a54 7
				configuration information. By default the Tcl
				directory is assumed to be in the location
				given by (a) above.
	--with-x=DIR		Tells configure where to find an installation
				of the X Window System. Not normally needed.
	--enable-threads	If this switch is set, Tk will compile itself
				with multithreading support.
d57 3
a59 3
				out how to do that on this platform. This is
				the default on platforms where we know how to
				build shared libraries.
d62 3
a64 5
	--disable-rpath		Turns off use of the rpath link option on
				platforms that would otherwise use it.
	--enable-symbols	Build with debugging symbols. By default
				standard debugging symbols are used. You can
				specify the value "mem" to include
d67 5
a75 4
	--disable-xft		Disable support for antialiased fonts via the
				Freetype/xft library. By default, this is
				switched on whenever the configure script can
				detect the required libraries.
d81 3
a83 4
				Add STRING to the name of each of the manual
				pages. If specified without giving STRING, the
				suffix will be "tk".

a84 1

d88 2
a89 2
				requires --enable-corefoundation with Tcl and
				Tk.
d91 34
a124 33
    Note: by default gcc will be used if it can be located on the PATH. If you
    want to use cc instead of gcc, set the CC environment variable to "cc"
    before running configure. It is not safe to change the Makefile to use gcc
    after configure is run.

    Note: be sure to use only absolute path names (those starting with "/") in
    the --prefix and --exec-prefix options.

(e) Type "make". This will create a library archive called "libtk<version>.a"
    or "libtk<version>.so" and an interpreter application called "wish" that
    allows you to type Tcl/Tk commands interactively or execute script files.
    It will also create a stub library archive "libtkstub<version>.a" that
    developers may link against other C code to produce loadable extensions
    that call into Tk's public interface routines.

(f) If the make fails then you'll have to personalize the Makefile for your
    site or possibly modify the distribution in other ways. First check the
    porting Web page above to see if there are hints for compiling on your
    system. If you need to modify Makefile, there are comments at the
    beginning of it that describe the things you might want to change and how
    to change them.

(g) Type "make install" to install Tk's binaries and script files in standard
    places. You'll need write permission on the installation directories to do
    this. The installation directories are determined by the "configure"
    script and may be specified with the --prefix and --exec-prefix options to
    "configure". See the Makefile for information on what directories were
    chosen. You should not override these choices by modifying the Makefile,
    or by copying files post-install. The installed binaries have embedded
    within them path values relative to the install directory. If you change
    your mind about where Tk should be installed, start this procedure over
    again from step (a) so that the path embedded in the binaries agrees with
    the install location.
d127 2
a128 2
    executable, or via the "make shell" target, and typing Tcl/Tk commands at
    the interactive prompt.
d131 4
a134 4
platforms. It contains information that people have provided about changes
they had to make to compile Tk in various environments. We're also interested
in hearing how to change the configuration setup so that Tk compiles on
additional platforms "out of the box".
d137 4
a140 3
variables in a production installation, as this can cause conflicts between
different versions of the libraries. Instead, the libraries should have the
correct locations of their associated script directories built into them.
d145 18
a162 17
Tk has a substantial self-test suite, consisting of a set of scripts in the
subdirectory "tests". To run the test suite just type "make test" in this
directory. You should then see a printout of the test files processed. If any
errors occur, you'll see a much more substantial printout for each error. In
order to avoid false error reports, be sure to run the tests with an empty
resource database (e.g., remove your .Xdefaults file or delete any entries
starting with *). Also, don't try to do anything else with your display or
keyboard while the tests are running, or you may get false violations. See the
README file in the "tests" directory for more information on the test suite.

If the test suite generates errors, most likely they are due to non-portable
tests that are interacting badly with your system configuration. We are
gradually eliminating the non-portable tests, but this release includes many
new tests so there will probably be some portability problems. As long as the
test suite doesn't core dump, it's probably safe to conclude that any errors
represent portability problems in the test suite and not fundamental flaws
with Tk.
d165 6
a170 8
Postscript generation, etc. These tests all have to be run by manually
enabling the "userInteraction" constraint when testing, and the results have
to be verified visually. This can be done with:

    make test TESTFLAGS="-constraints userInteraction"

Some tests will present a main window with a bunch of menus, which you can use
to select various tests.
@


1.21
log
@Removed support for Mac OS Classic platform [Patch 918139]
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.20 2003/03/04 23:50:44 dgp Exp $
d75 5
@


1.20
log
@        * README:                               Bumped version number of
        * generic/tk.h:                         Tk to 8.5a0.
        * library/tk.tcl:
        * mac/README:
        * macosx/Wish.pbproj/project.pbxproj:
        * unix/README:
        * unix/configure.in:
        * unix/tk.spec:
        * win/README:
        * win/configure.in:
        * win/makefile.vc:
        * win/tcl.m4:

        * unix/configure:      autoconf
        * win/configure:
@
text
@d21 1
a21 1
compile for a Macintosh, see the README file in the directory ../mac.
d23 1
a23 1
RCS: @@(#) $Id: README,v 1.19 2003/02/27 00:05:54 hobbs Exp $
@


1.19
log
@replace version refs with version-agnostic wording
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.18 2002/10/10 05:01:23 hobbs Exp $
d113 1
a113 1
    names, such as "wish8.4" or "libtk8.4.so"; to use the installed
d115 1
a115 1
    link (e.g. from "wish" to "wish8.4").
@


1.19.2.1
log
@update README files
@
text
@d21 1
a21 2
compile for Mac OS X, see the README file in the directory ../macosx.  To
compile for a classic Macintosh, see the README file in the directory ../mac.
d23 1
a23 1
RCS: @@(#) $Id: README,v 1.19 2003/02/27 00:05:54 hobbs Exp $
@


1.19.2.2
log
@documented macosx-only configure options.
@
text
@d24 1
a24 1
RCS: @@(#) $Id: README,v 1.19.2.1 2005/12/02 21:13:39 dgp Exp $
a75 5
    Mac OS X only: 
	--enable-framework	package Tk as a framework.
	--disable-corefoundation disable use of CoreFoundation API.
	--enable-aqua		use Aqua windowingsystem rather than X11,
				requires --enable-corefoundation with tcl & tk.
@


1.19.2.3
log
@        * unix/README:  Updates and typo corrections.  [Bug 1724841]
@
text
@d24 1
a24 1
RCS: @@(#) $Id: README,v 1.19.2.2 2005/12/03 00:36:51 das Exp $
d35 3
a37 1
(b) If you have already compiled Tk once in this directory and are now
d39 2
a40 2
    platform, type "make distclean" to discard all the configuration
    information computed previously.
d43 2
a44 2
    autoconf, which configures Tk for your system and creates a
    Makefile.  The configure script allows you to customize the Tk
d54 1
a54 1
	--enable-threads	If this switch is set, Tk will compile
d104 1
a104 1
    directories to do this.  The installation directories are
d139 1
a139 1
try to do anything else with your display or keyboard while the tests
@


1.18
log
@	* unix/README: doc'ed --enable-symbols options.
	* unix/Makefile.in: comment docs
	* unix/configure: regen
	* unix/tcl.m4: replaced SC_ENABLE_MEMDEBUG with a more intelligent
	SC_ENABLE_SYMBOLS that takes yes|no|mem|all as options now.
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.17 2002/09/27 18:09:53 dgp Exp $
d28 5
a32 4
(a) Make sure that the Tcl 8.4.1 release is present in the directory
    ../../tcl8.4.1 (or else use the "--with-tcl" switch described below). 
    This release of Tk will only work with Tcl 8.4. Also, be sure that
    you have configured Tcl before you configure Tk.
@


1.17
log
@        * README:               Bumped to version 8.4.1 to avoid confusion
        * generic/tk.h:         of CVS snapshots with release 8.4.0.
        * unix/README:
        * unix/configure.in:
        * unix/tk.spec
        * win/configure.in:

        * unix/configure:       autoconf
        * win/configure:
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.16 2002/07/24 18:42:23 hobbs Exp $
d61 4
a64 1
	--enable-symbols	build with debugging symbols
@


1.16
log
@	* unix/README: Corrected notes about running user interactive Tk
	tests. [Bug #462320]
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.15 2002/06/25 16:45:12 rmax Exp $
d28 2
a29 2
(a) Make sure that the Tcl 8.4 release is present in the directory
    ../../tcl8.4 (or else use the "--with-tcl" switch described below). 
@


1.15
log
@	* unix/tcl.m4:       New macro SC_CONFIG_MANPAGES.
	* unix/configure.in: Added support for symlinks and compression
	* unix/Makefile.in:  when installing the manpages. [Patch 518052]
	                     Default is still hardlinks and no compression.

	* unix/mkLinks:      generated
	* unix/configure:

	* unix/README:       Added documentation for the new features.
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.14 2002/03/05 20:34:15 hobbs Exp $
d142 6
a147 4
Postscript generation, etc.  These tests all have to be run manually and
the results have to be verified visually.  To run the tests, cd to the
"tests" directory and run the script "visual".  It will present a main
window with a bunch of menus, which you can use to select various tests.
@


1.14
log
@added --* options docs
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.13 2002/03/04 23:31:45 hobbs Exp $
d67 4
@


1.13
log
@updated to use www.tcl.tk URL
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.12 2001/07/05 17:23:53 hobbs Exp $
a46 2
	--enable-threads	Tk on Unix currently does not support
				threaded builds.
d52 2
d61 6
@


1.12
log
@updated README with purls
@
text
@d9 1
a9 1
	http://www.purl.org/tcl/home/doc/howto/compile.html
d13 1
a13 1
	http://www.purl.org/tcl/home/software/tcltk/platforms.html
d23 1
a23 1
RCS: @@(#) $Id: README,v 1.11 2000/08/25 05:55:05 mo Exp $
@


1.12.2.1
log
@Merging with TOT as of 06/09/2002.
@
text
@d9 1
a9 1
	http://www.tcl.tk/doc/howto/compile.html
d13 1
a13 1
	http://www.tcl.tk/software/tcltk/platforms.html
d23 1
a23 1
RCS: @@(#) $Id$
d47 2
a53 2
	--enable-threads	If this switch is set, Tcl will compile
				itself with multithreading support.
a60 6
	--enable-symbols	build with debugging symbols
	--disable-symbols	build without debugging symbols
	--enable-64bit		enable 64bit support (where applicable)
	--disable-64bit		disable 64bit support (where applicable)
	--enable-64bit-vis	enable 64bit Sparc VIS support
	--disable-64bit-vis	disable 64bit Sparc VIS support
@


1.12.2.2
log
@merged with trunk at tag macosx-8-4-merge-2002-08-20-trunk
@
text
@a66 4
	--enable-man-symlinks	Use symlinks for linking the manpages that
				should be reachable under several names.
	--enable-man-compression=PROG
				Compress the manpages using PROG.
d138 4
a141 6
Postscript generation, etc.  These tests all have to be run by manually
enabling the "userInteraction" constraint when testing, and the results
have to be verified visually..  This can be done with
     make test TESTFLAGS="-constraints userInteraction"
Some tests will present a main window with a bunch of menus, which you can
use to select various tests.
@


1.11
log
@remove --enable-gcc configure option
@
text
@d9 1
a9 1
	http://dev.scriptics.com/doc/howto/compile.html
d13 1
a13 1
	http://dev.scriptics.com/software/tcltk/platforms.html
d23 1
a23 1
RCS: @@(#) $Id: README,v 1.10 2000/05/03 00:18:36 hobbs Exp $
d68 1
a68 1
    in the --prefix and --exec_prefix options.
d86 1
a86 1
    the --prefix and --exec_prefix options to "configure".  See the
@


1.11.2.1
log
@sync with head
@
text
@d9 1
a9 1
	http://www.tcl.tk/doc/howto/compile.html
d13 1
a13 1
	http://www.tcl.tk/software/tcltk/platforms.html
d23 1
a23 1
RCS: @@(#) $Id: README,v 1.14 2002/03/05 20:34:15 hobbs Exp $
d47 2
a53 2
	--enable-threads	If this switch is set, Tcl will compile
				itself with multithreading support.
a60 6
	--enable-symbols	build with debugging symbols
	--disable-symbols	build without debugging symbols
	--enable-64bit		enable 64bit support (where applicable)
	--disable-64bit		disable 64bit support (where applicable)
	--enable-64bit-vis	enable 64bit Sparc VIS support
	--disable-64bit-vis	disable 64bit Sparc VIS support
d68 1
a68 1
    in the --prefix and --exec-prefix options.
d86 1
a86 1
    the --prefix and --exec-prefix options to "configure".  See the
@


1.11.4.1
log
@	* Merged updates from HEAD.
@
text
@d9 1
a9 1
	http://www.purl.org/tcl/home/doc/howto/compile.html
d13 1
a13 1
	http://www.purl.org/tcl/home/software/tcltk/platforms.html
d23 1
a23 1
RCS: @@(#) $Id: README,v 1.12 2001/07/05 17:23:53 hobbs Exp $
d68 1
a68 1
    in the --prefix and --exec-prefix options.
d86 1
a86 1
    the --prefix and --exec-prefix options to "configure".  See the
@


1.10
log
@	* README:
	* generic/tk.h:
	* library/tk.tcl:
	* mac/README:
	* unix/README:
	* unix/configure.in:
	* unix/tk.spec:
	* win/README:
	* win/aclocal.m4:
	* win/configure.in:
	* win/makefile.vc: updated patchlevel to 8.4a1
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.9 2000/04/26 17:37:35 hobbs Exp $
a46 4
	--enable-gcc		If this switch is set, Tk will configure
				itself to use gcc if it is available on your
				system.  Note:  it is not safe to modify the
				Makefile to use gcc after configure is run.
d61 6
@


1.9
log
@	* README:
	* mac/README:
	* unix/README:
	* unix/tk.spec:
	* win/README: Updating URLs to reference dev.scriptics.com
@
text
@d23 1
a23 1
RCS: @@(#) $Id: README,v 1.8 2000/02/10 08:53:15 hobbs Exp $
d28 3
a30 3
(a) Make sure that the Tcl 8.3 release is present in the directory
    ../../tcl8.3 (or else use the "--with-tcl" switch described below). 
    This release of Tk will only work with Tcl 8.3. Also, be sure that
d97 1
a97 1
    names, such as "wish8.3" or "libtk8.3.so"; to use the installed
d99 1
a99 1
    link (e.g. from "wish" to "wish8.3").
@


1.9.2.1
log
@updated patchlevel to 8.3.4.
updated READMEs to point to www.tcl-tk.net where applicable.
added proper Win64 support to makefiles.
@
text
@d9 1
a9 1
	http://www.tcl-tk.net/doc/howto/compile.html
d13 1
a13 1
	http://www.tcl-tk.net/software/tcltk/platforms.html
d23 1
a23 1
RCS: @@(#) $Id: README,v 1.9 2000/04/26 17:37:35 hobbs Exp $
@


1.9.2.2
log
@	* README:           updated to 8.3.5 patchlevel
	* generic/tk.h:     pointed README urls at www.tcl.tk
	* mac/README:
	* unix/README:
	* unix/configure:
	* unix/configure.in:
	* unix/tcl.m4:
	* unix/tk.spec:
	* win/README:
	* win/configure:
	* win/configure.in:
	* win/tcl.m4:
@
text
@d9 1
a9 1
	http://www.tcl.tk/doc/howto/compile.html
d13 1
a13 1
	http://www.tcl.tk/software/tcltk/platforms.html
d23 1
a23 1
RCS: @@(#) $Id: README,v 1.9.2.1 2001/10/03 22:04:52 hobbs Exp $
@


1.8
log
@	* unix/tkUnixWm.c (Tk_CoordsToWindow): qualified delete of error
	handler as the goto label is reached from above and below.

	* unix/configure.in:
	* unix/aclocal.m4: cleaned up macros to coincide with tcl.m4,
	added -export-dynamic to LDFLAGS for FreeBSD-3+ [Bug: 2998]

	* unix/README:
	* unix/Makefile.in (dist): removed porting.notes and porting.old
	from distribution and CVS.  The information was very outdated.  Now
	refer to http://dev.scriptics.com/services/support/platforms.html
@
text
@d9 1
a9 1
	http://www.scriptics.com/support/howto/compile.html
d13 1
a13 1
	http://dev.scriptics.com/services/support/platforms.html
d23 1
a23 1
RCS: @@(#) $Id: README,v 1.7 1999/10/01 22:45:27 hobbs Exp $
@


1.7
log
@1999-09-24  Jeff Hobbs  <hobbs@@scriptics.com>

	* */README:
	* win/makefile.vc:
	* */configure.in:
	* generic/tk.h:
	* library/tk.tcl: up'd to 8.3a1

	* unix/Makefile.in: changed 'mkdir' to 'mkdir -p'

	* library/dialog.tcl: changed {Times 18} to {Times 12} for
	dialog font.
@
text
@d9 5
a13 1
    http://www.scriptics.com/support/howto/compile.html
d23 1
a23 1
RCS: @@(#) $Id: README,v 1.6 1999/06/25 23:30:26 welch Exp $
d51 2
d60 5
a64 1
				out how to do that on this platform.
d68 4
a71 3
(e) Type "make".  This will create a library archive called "libtk.a"
    or "libtk.so" and an interpreter application called "wish" that
    allows you to type Tcl commands interactively or execute script files.
d75 2
a76 3
    First check the file "porting.notes" to see if there are hints
    for compiling on your system.  Then look at the porting Web page
    described later in this file.  If you need to modify Makefile,
d101 5
a105 5
If you have trouble compiling Tk, read through the file
"porting.notes".  It contains information that people have provided
about changes they had to make to compile Tcl in various environments.
We're also interested in hearing how to change the configuration setup
so that Tcl compiles on additional platforms "out of the box".
@


1.6
log
@Changed to Tk 8.2b1
@
text
@d19 1
a19 1
RCS: @@(#) $Id: README,v 1.5 1999/04/24 01:50:51 stanton Exp $
d24 3
a26 3
(a) Make sure that the Tcl 8.2 release is present in the directory
    ../../tcl8.2 (or else use the "--with-tcl" switch described below). 
    This release of Tk will only work with Tcl 8.2. Also, be sure that
d87 1
a87 1
    names, such as "wish8.2" or "libtk8.2.so"; to use the installed
d89 1
a89 1
    link (e.g. from "wish" to "wish8.2").
@


1.5
log
@merged 8.1.0 changes into mainline
@
text
@d19 1
a19 1
RCS: @@(#) $Id: README,v 1.4 1999/04/16 01:51:45 stanton Exp $
d24 3
a26 3
(a) Make sure that the Tcl 8.1 release is present in the directory
    ../../tcl8.1 (or else use the "--with-tcl" switch described below). 
    This release of Tk will only work with Tcl 8.1. Also, be sure that
d87 1
a87 1
    names, such as "wish8.1" or "libtk8.1.so"; to use the installed
d89 1
a89 1
    link (e.g. from "wish" to "wish8.1").
@


1.4
log
@* Merged 8.1 branch into the main trunk
@
text
@d1 3
d8 3
d19 1
a19 1
RCS: @@(#) $Id$
d25 1
a25 1
    ../../tcl8.1a2 (or else use the "--with-tcl" switch described below). 
@


1.4.4.1
log
@Trimmed out release-specific information from the READMEs and added
several pointers into the Scriptics web site.
@
text
@a0 3
Tk UNIX README
--------------

a4 3
The information in this file is maintained at:
    http://www.scriptics.com/support/howto/compile.html

d13 1
a13 1
RCS: @@(#) $Id: README,v 1.4 1999/04/16 01:51:45 stanton Exp $
d19 1
a19 1
    ../../tcl8.1 (or else use the "--with-tcl" switch described below). 
@


1.3
log
@updated readmes for 8.0.5 release
@
text
@d13 1
a13 1
RCS: @@(#) $Id: README,v 1.2 1998/09/14 18:23:54 stanton Exp $
d18 3
a20 3
(a) Make sure that the Tcl 8.0 release is present in the directory
    ../../tcl8.0 (or else use the "--with-tcl" switch described below). 
    This release of Tk will only work with Tcl 8.0. Also, be sure that
d81 1
a81 1
    names, such as "wish8.0" or "libtk8.0.so"; to use the installed
d83 1
a83 1
    link (e.g. from "wish" to "wish8.0").
@


1.2
log
@Replaced SCCS strings, fixed binary files
@
text
@d13 1
a13 1
RCS: @@(#) $Id$
d85 5
a89 13
If you have trouble compiling Tk, read through the file "porting.notes".
It contains information that people have provided about changes they had
to make to compile Tcl in various environments.  Or, check out the
following Web URL:
    http://www.sunlabs.com/cgi-bin/tcl/info.8.0
This is an on-line database of porting information.  We make no guarantees
that this information is accurate, complete, or up-to-date, but you may
find it useful.  If you get Tk running on a new configuration and had to
make non-trivial changes to do it, we'd be happy to receive new information
to add to "porting.notes".  You can also make a new entry into the
on-line Web database.  We're also interested in hearing how to change the
configuration setup so that Tcl compiles on additional platforms "out of
the box".
@


1.1
log
@Initial revision
@
text
@d13 1
a13 1
SCCS: @@(#) README 1.24 97/08/13 17:31:19
@


1.1.4.1
log
@initial tk8.1a2 version
@
text
@d13 1
a13 1
SCCS: @@(#) README 1.26 98/02/18 18:04:01
d18 3
a20 3
(a) Make sure that the Tcl 8.1 release is present in the directory
    ../../tcl8.1a2 (or else use the "--with-tcl" switch described below). 
    This release of Tk will only work with Tcl 8.1. Also, be sure that
d81 1
a81 1
    names, such as "wish8.1" or "libtk8.1.so"; to use the installed
d83 1
a83 1
    link (e.g. from "wish" to "wish8.1").
d89 1
a89 1
    http://www.sunlabs.com/cgi-bin/tcl/info.8.1
@


1.1.4.2
log
@Merged 8.0.3 changes into 8.1
@
text
@d13 1
a13 1
RCS: @@(#) $Id: README,v 1.2 1998/09/14 18:23:54 stanton Exp $
@


1.1.4.3
log
@* Various cleanup related to the Tcl_Eval and Tcl_ObjSetVar
changes in Tcl.

* Integrated patches from 8.0.5b2
@
text
@d13 1
a13 1
RCS: @@(#) $Id: README,v 1.1.4.2 1998/09/30 02:19:10 stanton Exp $
d85 13
a97 5
If you have trouble compiling Tk, read through the file
"porting.notes".  It contains information that people have provided
about changes they had to make to compile Tcl in various environments.
We're also interested in hearing how to change the configuration setup
so that Tcl compiles on additional platforms "out of the box".
@


