As it turns out, Fossil didn’t really have Tcl enabled when I was running my TH1 test script.
Running “fossil version -v” forces the Tcl interpreter to load and thus reports that the Tcl interpreter is loaded along with its version. However, when I run a test script with "fossil test-th-source --th-trace ~/test.th1” that isn’t the case. The test-th-source command apparently requires you to use the option --open-config so it can read the “tcl” setting from the configuration database and load the interpreter if needed. Running my TH1 test script with the following command works great. fossil test-th-source --th-trace --open-config ~/test.th1 Then, as far as testing a script through the UI via Admin -> TH1, I was getting my wires crossed. I didn’t actually have the “tcl” setting turned on in the repository I cared about — it was turned on elsewhere. I can now successfully run TH1 scripts with Tcl integration in all contexts that I care about. The last thing that is currently unsolved is that when I build Fossil as a statically linked binary with Tcl integration, Fossil crashes when loading libtcl8.6.so. Any thoughts? > On Mar 16, 2017, at 7:03 PM, Joe Mistachkin <[email protected]> wrote: > > > How was the Tcl library built? Are you able to step through Fossil in gdb to > see why tclInvoke is not getting added to the TH1 interpreter? > > Sent from my iPhone > https://urn.to/r/mistachkin > > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
