|
1 This directory contains source code to |
|
2 |
|
3 SQLite: An Embeddable SQL Database Engine |
|
4 |
|
5 To compile the project, first create a directory in which to place |
|
6 the build products. It is recommended, but not required, that the |
|
7 build directory be separate from the source directory. Cd into the |
|
8 build directory and then from the build directory run the configure |
|
9 script found at the root of the source tree. Then run "make". |
|
10 |
|
11 For example: |
|
12 |
|
13 tar xzf sqlite.tar.gz ;# Unpack the source tree into "sqlite" |
|
14 mkdir bld ;# Build will occur in a sibling directory |
|
15 cd bld ;# Change to the build directory |
|
16 ../sqlite/configure ;# Run the configure script |
|
17 make ;# Run the makefile. |
|
18 make install ;# (Optional) Install the build products |
|
19 |
|
20 The configure script uses autoconf 2.61 and libtool. If the configure |
|
21 script does not work out for you, there is a generic makefile named |
|
22 "Makefile.linux-gcc" in the top directory of the source tree that you |
|
23 can copy and edit to suit your needs. Comments on the generic makefile |
|
24 show what changes are needed. |
|
25 |
|
26 The linux binaries on the website are created using the generic makefile, |
|
27 not the configure script. The windows binaries on the website are created |
|
28 using MinGW32 configured as a cross-compiler running under Linux. For |
|
29 details, see the ./publish.sh script at the top-level of the source tree. |
|
30 The developers do not use teh configure script. |
|
31 |
|
32 SQLite does not require TCL to run, but a TCL installation is required |
|
33 by the makefiles. SQLite contains a lot of generated code and TCL is |
|
34 used to do much of that code generation. The makefile also requires |
|
35 AWK. |
|
36 |
|
37 Contacts: |
|
38 |
|
39 http://www.sqlite.org/ |