| 1 | | Perhaps there could be a `--with-bundled-tcl` flag for the configure script to control whether the bundled tcl gets built or not? Or a `--with-tcl-prefix=` flag to control which already-installed copy of Tcl gets used, if any? There are already precedents for both in MacPorts, as I remember there being a `--with-included-tclthread` flag previously, and there are also `--with-curlprefix` and `--with-sqlite3prefix` flags for choosing the prefix of curl and sqlite3 respectively... |
| | 1 | Perhaps there could be a "`--with-bundled-tcl`" flag for the configure script to control whether the bundled tcl gets built or not? |
| | 2 | Or a "`--with-tcl-prefix=`" flag to control which already-installed copy of Tcl gets used, if any? |
| | 3 | There are already precedents for both in MacPorts, as I remember there being a "`--with-included-tclthread`" flag previously, and there are also "`--with-curlprefix`" and "`--with-sqlite3prefix`" flags for choosing the prefix of curl and sqlite3 respectively... |
