Test Procedures For The SQLite TCL Extension

1.0 Background

The SQLite TCL extension logic (in the “tclsqlite.c” source file) is statically linked into “textfixture” executable which is the program used to do most of the testing associated with “make test”, “make devtest”, and/or “make releasetest”. So the functionality of the SQLite TCL extension is thoroughly vetted during normal testing. The procedures below are designed to test the loadable extension aspect of the SQLite TCL extension, and in particular to verify that the “make tclextension-install” build target works and that an ordinary tclsh can subsequently run “package require sqlite3”.

This procedure can also be used as a template for how to set up a local TCL+SQLite development environment. In other words, it can be be used as a guide on how to compile per-user copies of Tcl that are used to develop, test, and debug SQLite. In that case, perhaps make minor changes to the procedure such as:

  • Make TCLBUILD directory is permanent.
  • Enable debugging symbols on the Tcl library build.
  • Reduce the optimization level to -O0 for easier debugging.
  • Also compile “wish” to go with each “tclsh”.

2.0 Testing On Unix-like Systems (Including Mac)

See also the document which provides another perspective on how to compile SQLite on unix-like systems.

2.1 Setup

2.2 Testing TCL 8.6 on unix

2.3 Testing TCL 9.0 on unix

2.4 Cleanup

3.0 Testing On Windows

See also the document which provides another perspective on how to compile SQLite on Windows.

3.1 Setup for Windows

3.2 Testing TCL 8.6 on Windows

3.3 Testing TCL 9.0 on Windows

3.4 Cleanup