Distributions of the
are available from the SourceForge download
area at http://sourceforge.net/projects/tarray/files.
tarray-bin-VERSION.zip, and optionally
These contain both 32- and 64-bit binaries for Windows.
Unpack the distributions into any directory present in the
For other (Unix-like) platforms, the
packages are distributed as TEA-compatible
To install an extension, extract into a directory and from the
top level directory run the following commands in the shell.
./configure --with-tcl=PATHTOTCLDIR make install
where PATHTOTCLDIR is the full path to the directory containing
tclconfig.sh file for the Tcl installation. Note there is no
need for a standalone
make command since the
make install does the
actual build as well as install.
tarray_ui package, distributed as
is a pure Tcl package and can be extracted into any directory that
is included in the Tcl
xtal extensions are built using the
Download a copy of the
tarraysources by either cloning its Mercurial repository or downloading a snapshot of the sources. See https://sourceforge.net/p/tarray/code/ci/tip/tree/ for details.
Download and install the
critclpackage (3.1 or later) as described in http://andreas-kupries.github.com/critcl/doc/files/critcl_installer.html.
Set up your compiler environment, for example, running the
vcvars.batfile on Windows.
Change to the
srcdirectory in the
tarraysource distribution and run a command of the form
tclsh build.tcl extension ?-target TARGETNAME?
This will build the
To build the
change to the
xtal directory and again run the same command as above.
If specified, TARGETNAME should be one of the supported
critcl build targets. Naturally, the build environment should
reflect the chosen target. If unspecified, it defaults to whatever
critcl guesses to be the host platform.
Finally, to build the
tarray_ui pure Tcl package, change to the
directory and run the command
tclsh build.tcl package
This will create the
build directory in your source tree.
You can of course create your own build scripts with different
Critcl options using the
build.tcl file as a template.
Windows builds have support for parallelized operations using
the native Win32 thread API’s.
To build parallelized versions for Unix/Linux platforms,
libdispatch library has to be present on the system.
If this library is not detected, the extension will not parallelize
any operations. This library can be installed using the system’s
package manager on most Linux systems.
In the 0.9 release, the