Small. Fast. Reliable.
Choose any three.
Choose any three.
Build products are named using one of the following templates:
Templates (1) and (2) are used for source-code products. Template (1) is used for generic source-code products and templates (2) is used for source-code products that are generally only useful on unix-like platforms. Template (3) is used for precompiled binaries products. Template (4) is used for unofficial pre-release "snapshots" of source code.
The version is encoded so that filenames sort in order of increasing version number when viewed using "ls". For version 3.X.Y the filename encoding is 3XXYY00. For branch version 3.X.Y.Z, the encoding is 3XXYYZZ.
The date in template (4) is of the form: YYYYMMDDHHMM
The SQLite source code is maintained in three geographically-dispersed self-synchronizing Fossil repositories that are available for anonymous read-only access. Anyone can view the repository contents and download historical versions of individual files or ZIP archives of historical check-ins. You can also clone the entire repository.
See the How To Compile SQLite page for additional information on how to use the raw SQLite source code. Note that a recent version of Tcl is required in order to build from the repository sources. The amalgamation source code files (the "sqlite3.c" and "sqlite3.h" files) build products and are not contained in raw source code tree.
https://www.sqlite.org/cgi/src (Dallas)
https://www2.sqlite.org/cgi/src (Newark)
https://www3.sqlite.org/cgi/src (San Francisco)
The documentation is maintained in separate Fossil repositories located at:
https://www.sqlite.org/cgi/docsrc (Dallas)
https://www2.sqlite.org/cgi/docsrc (Newark)
https://www3.sqlite.org/cgi/docsrc (San Francisco)