michael@0: This directory contains source code to michael@0: michael@0: SQLite: An Embeddable SQL Database Engine michael@0: michael@0: To compile the project, first create a directory in which to place michael@0: the build products. It is recommended, but not required, that the michael@0: build directory be separate from the source directory. Cd into the michael@0: build directory and then from the build directory run the configure michael@0: script found at the root of the source tree. Then run "make". michael@0: michael@0: For example: michael@0: michael@0: tar xzf sqlite.tar.gz ;# Unpack the source tree into "sqlite" michael@0: mkdir bld ;# Build will occur in a sibling directory michael@0: cd bld ;# Change to the build directory michael@0: ../sqlite/configure ;# Run the configure script michael@0: make ;# Run the makefile. michael@0: make install ;# (Optional) Install the build products michael@0: michael@0: The configure script uses autoconf 2.61 and libtool. If the configure michael@0: script does not work out for you, there is a generic makefile named michael@0: "Makefile.linux-gcc" in the top directory of the source tree that you michael@0: can copy and edit to suit your needs. Comments on the generic makefile michael@0: show what changes are needed. michael@0: michael@0: The linux binaries on the website are created using the generic makefile, michael@0: not the configure script. The windows binaries on the website are created michael@0: using MinGW32 configured as a cross-compiler running under Linux. For michael@0: details, see the ./publish.sh script at the top-level of the source tree. michael@0: The developers do not use teh configure script. michael@0: michael@0: SQLite does not require TCL to run, but a TCL installation is required michael@0: by the makefiles. SQLite contains a lot of generated code and TCL is michael@0: used to do much of that code generation. The makefile also requires michael@0: AWK. michael@0: michael@0: Contacts: michael@0: michael@0: http://www.sqlite.org/