mirror of
https://github.com/sqlite/sqlite.git
synced 2024-11-22 12:17:40 +01:00
79 lines
3.0 KiB
Plaintext
79 lines
3.0 KiB
Plaintext
This is the SQLite extension for Tcl using the Tcl Extension
|
|
Architecture (TEA).
|
|
|
|
----------------------- A BETTER WAY ---------------------------
|
|
|
|
A better way to build the TCL extension for SQLite is to use the
|
|
canonical source code tarball. For Unix:
|
|
|
|
./configure --with-tclsh=$(TCLSH)
|
|
make tclextension-install
|
|
|
|
For Windows:
|
|
|
|
nmake /f Makefile.msc tclextension-install TCLSH_CMD=$(TCLSH)
|
|
|
|
In both of the above, replace $(TCLSH) with the full pathname of
|
|
of the tclsh that you want the SQLite extension to work with. See
|
|
step-by-step instructions at the links below for more information:
|
|
|
|
https://sqlite.org/src/doc/trunk/doc/compile-for-unix.md
|
|
https://sqlite.org/src/doc/trunk/doc/compile-for-windows.md
|
|
|
|
The whole point of the amalgamation-autoconf tarball (in which this
|
|
README.txt file is embedded) is to provide a means of compiling
|
|
SQLite that does not require first installing TCL and/or "tclsh".
|
|
The canonical Makefile in the SQLite source tree provides more
|
|
capabilities (such as the the ability to run test cases to ensure
|
|
that the build worked) and is better maintained. The only
|
|
downside of the canonical Makfile is that it requires a TCL
|
|
installation. But if you are wanting to build the TCL extension for
|
|
SQLite, then presumably you already have a TCL installation. So why
|
|
not just use the more-capable and better-maintained canoncal Makefile?
|
|
|
|
This TEA builder is derived from code found at
|
|
|
|
http://core.tcl-lang.org/tclconfig
|
|
http://core.tcl-lang.org/sampleextension
|
|
|
|
The SQLite developers do not understand how it works. It seems to
|
|
work for us. It might also work for you. But we cannot promise that.
|
|
|
|
If you want to use this TEA builder and it works for you, that's fine.
|
|
But if you have trouble, the first thing you should do is go back
|
|
to using the canonical Makefile in the SQLite source tree.
|
|
|
|
------------------------------------------------------------------
|
|
|
|
|
|
UNIX BUILD
|
|
==========
|
|
|
|
Building under most UNIX systems is easy, just run the configure script
|
|
and then run make. For more information about the build process, see
|
|
the tcl/unix/README file in the Tcl src dist. The following minimal
|
|
example will install the extension in the /opt/tcl directory.
|
|
|
|
$ cd sqlite-*-tea
|
|
$ ./configure --prefix=/opt/tcl
|
|
$ make
|
|
$ make install
|
|
|
|
WINDOWS BUILD
|
|
=============
|
|
|
|
The recommended method to build extensions under windows is to use the
|
|
Msys + Mingw build process. This provides a Unix-style build while
|
|
generating native Windows binaries. Using the Msys + Mingw build tools
|
|
means that you can use the same configure script as per the Unix build
|
|
to create a Makefile. See the tcl/win/README file for the URL of
|
|
the Msys + Mingw download.
|
|
|
|
If you have VC++ then you may wish to use the files in the win
|
|
subdirectory and build the extension using just VC++. These files have
|
|
been designed to be as generic as possible but will require some
|
|
additional maintenance by the project developer to synchronise with
|
|
the TEA configure.in and Makefile.in files. Instructions for using the
|
|
VC++ makefile are written in the first part of the Makefile.vc
|
|
file.
|