blob: e35a5bcf41357917588b5fd9b98a7435b002a873 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
## SECTION=bytecode_engines
menuconfig TCL
tristate
prompt "tcl "
select LIBC_M
select LIBC_DL
select LIBC_PTHREAD
select GCCLIBS_GCC_S
help
From the FAQ (refer http://tcl.sourceforge.net/faqs/):
Tcl and Tk originated with Dr. John Ousterhout while teaching at the
University of California, Berkeley, California.
[...]
Dr. Ousterhout got the idea for Tcl while on sabbatical leave at
DEC's Western Research Laboratory in the fall of 1987. He started
actually implementing it when he got back to Berkeley in the spring
of 1988; by summer of that year it was in use in some internal
applications, but there was no Tk. The first external releases of
Tcl were in 1989. Tk implemention began in 1989, and the first
release of Tk was in 1991. [...]
The current implementation uses a byte code interpreter and runtime
compilation.
Note: To install this package you must have a working TCL on your
host (only required for the install stage).
if TCL
config TCL_THREADS
bool
prompt "enable thread support"
help
Build the TCL engine with thread support. This may speed down non
thread scripts.
config TCL_ENCODING
bool
prompt "install encodings"
help
Install support for various encodings (iso8859-1, iso8859-15,
cp437, cp850, ascii, big5).
config TCL_TESTING
bool
prompt "prepare for testing"
help
If your are a ptxdist user only, leave this entry unchecked.
Enable this if you are a ptxdist developer and you want to run the
TCL test suite on your target to check if this TCL port is correct.
To run the test suite, run single tests from '/usr/share/tcl-tests'
or run the whole suite with '/usr/share/tcl-tests/all.tcl' from
inside a tcl shell.
endif
|