summaryrefslogtreecommitdiff
path: root/ext/tcltklib/README.ActiveTcl
diff options
context:
space:
mode:
Diffstat (limited to 'ext/tcltklib/README.ActiveTcl')
-rw-r--r--ext/tcltklib/README.ActiveTcl27
1 files changed, 17 insertions, 10 deletions
diff --git a/ext/tcltklib/README.ActiveTcl b/ext/tcltklib/README.ActiveTcl
index c9cc691973..42dcc72af5 100644
--- a/ext/tcltklib/README.ActiveTcl
+++ b/ext/tcltklib/README.ActiveTcl
@@ -24,16 +24,23 @@ For example, when you install ActiveTcl-8.4.x to '/usr/local/ActiveTcl',
--enable-tcltk-stubs
It depends on your environment that you have to add the directory of
-ActiveTcl's dynamic link libraries to your library path when execute
-Ruby/Tk.
-
-# For example, on Linux, one of the ways is to use LD_LIBRARY_PATH
-# environment variable.
-#
-# [bash]$ LD_LIBRARY_PATH=/usr/local/ActiveTcl/lib:$LD_LIBRARY_PATH \
-# ruby your-Ruby/Tk-script
-#
-# [bash]$ LD_LIBRARY_PATH=/usr/local/ActiveTcl/lib:$LD_LIBRARY_PATH irb
+ActiveTcl's libraries to your library path when execute Ruby/Tk.
+One of the way is to add entries to TCLLIBPATH environment variable,
+and one of the others add to LD_LIBRARY_PATH environment variable
+
+Probably, using TCLLIBPATH is better. The value is appended at the
+head of Tcl's 'auto_path' variable. You can see the value of the
+variable by using 'Tk::AUTO_PATH.value' or 'Tk::AUTO_PATH.list'.
+
+For example, on Linux, one of the ways is to use LD_LIBRARY_PATH
+environment variable.
+-------------------------------------------------------------------------
+ [bash]$ LD_LIBRARY_PATH=/usr/local/ActiveTcl/lib:$LD_LIBRARY_PATH \
+ ruby your-Ruby/Tk-script
+
+ [bash]$ LD_LIBRARY_PATH=/usr/local/ActiveTcl/lib:$LD_LIBRARY_PATH irb
+-------------------------------------------------------------------------
+Based on it, the Tcl interpreter changes auto_path variable's value.
Then, you'll be able to use Tcl/Tk extension libraries included in the
ActiveTcl package (e.g. call TkPackage.require('BWidget'), and then,