SQLite Download Page

hd_keywords {download page} proc Product {pattern desc {frag {}}} { regsub VVV $pattern {*} p3 regsub DATE $p3 {20*} p3 regsub VVV $pattern {(30\d{5})} pattern regsub DATE $pattern {(\d{12})} pattern set p2 [string map {* .*} $pattern] set flist [glob -nocomplain $p3] foreach file [lsort -dict $flist] { if {![regexp ^$p2\$ $file all version]} continue if {[regexp {^(\d\d\d\d)(\d\d)(\d\d)(\d\d)(\d\d)$} $version \ all year month day hour min]} { set version "$year-$month-$day $hour:$min UTC" } elseif {[regexp {^30(\d)(\d\d)(\d\d)$} $version \ all major minor patch]} { scan $major %d m1 scan $minor %d m2 scan $patch %d m3 set version 3.$m1.$m2 if {$patch>0} { append version .$m3 } } set size [file size $file] set sha1sum [lindex [exec sha1sum $file] 0] set units bytes if {$size>1024*1024} { set size [format %.2f [expr {$size/(1024.0*1024.0)}]] set units MiB } elseif {$size>1024} { set size [format %.2f [expr {$size/(1024.0)}]] set units KiB } global pending_heading if {$pending_heading!=""} { hd_puts "" set pending_heading {} } hd_puts "" hd_puts "" hd_puts "" regsub -all VERSION $desc $version d2 hd_puts "" } if {$frag!=""} { eval hd_keywords [lrange $frag 1 end] } } cd $::DEST proc Heading {title} { set ::pending_heading $title # hd_puts "" } Heading {Pre-release Source Code Snapshots} Product {sqlite-amalgamation-DATE.zip} { This is a snapshot (as of VERSION) of the current SQLite code under development. Use this snapshot for testing only. This is not a release. This ZIP archive contains all preprocessed C code combined into a single source file (the amalgamation). } Product {sqlite-amalgamation32k-DATE.zip} { This is a snapshot (as of VERSION) of the current SQLite code under development. The code is split into a small number of source files, such that no source files is longer than 32767 lines of code. Use this snapshot for testing only. This is not a release. } Product {sqlite-tea-DATE.zip} { This is a snapshot (as of VERSION) of the current SQLite code under development, packaged and ready to build using the Tcl Extension Architecture (TEA). Use this snapshot for testing only. This is not a release. } Product {sqlite-shell-win32-x86-DATE.zip} { This is a snapshot (as of VERSION) build of the sqlite3.exe command-line shell shell program for 32-bit windows. } Product {sqlite-shell-win64-x64-DATE.zip} { This is a snapshot (as of VERSION) build of the sqlite3.exe command-line shell shell program for 64-bit windows. } Heading {Source Code} Product {sqlite-amalgamation-VVV.zip} { This ZIP archive contains all C source code for SQLite VERSION combined into a single source file (the amalgamation). } Product {sqlite-amalgamation32k-VVV.zip} { This ZIP archive contains all C source code for SQLite VERSION combined into a small number of source files, where no source file is longer than 32767 lines of code. } Product {sqlite-autoconf-VVV.tar.gz} { A tarball containing the amalgamation for SQLite VERSION together with an configure script and makefile for building it. This tarball also contains in the "tea" subdirectory a separate configure script and makefile compatible with the Tcl Extension Architecture (TEA) for building the TCL bindings to SQLite. } {amalgtarball {amalgamation tarball}} Product {sqlite-tea-VVV.tar.gz} { A tarball of the amalgamation together with a Tcl Extension Architecture (TEA) compatible configure script and makefile. } {teatarball {TEA tarball}} Heading {Documentation} Product {sqlite-doc-VVV.zip} { This ZIP archive contains most of the static HTML files that comprise this website, including all of the SQL Syntax and the C/C++ interface specs and other miscellaneous documentation. } Heading {Precompiled Binaries for Linux} Product sqlite-shell-linux-x86-VVV.zip { A command-line shell for accessing and modifying SQLite databases. This program is compatible with all versions of SQLite through VERSION and beyond. } Product sqlite-analyzer-linux-x86-VVV.zip { An analysis program for database files compatible with all SQLite versions through VERSION and beyond. } Heading {Precompiled Binaries For Mac OS X (x86)} Product sqlite-shell-mac-x86-VVV.zip { A command-line shell for accessing and modifying SQLite databases. This program is compatible with all versions of SQLite through VERSION and beyond. } Product sqlite-analyzer-mac-x86-VVV.zip { An analysis program for database files compatible with all SQLite versions through VERSION and beyond. } Heading {Precompiled Binaries For Windows} Product sqlite-shell-win32-x86-VVV.zip { A command-line shell for accessing and modifying SQLite databases. This program is compatible with all versions of SQLite through VERSION and beyond. } Product sqlite-dll-win32-x86-VVV.zip { This ZIP archive contains a DLL for the SQLite library version VERSION. } Product sqlite-analyzer-win32-x86-VVV.zip { An analysis program for database files compatible with all SQLite versions through VERSION and beyond. } Heading {Legacy Source Code Distribution Formats (Not Recommended)} Product {sqlite-src-VVV.zip} { A ZIP archive of the complete source tree for SQLite version VERSION as extracted from the version control system. The Makefile and configure script in this tarball are not supported. Their use is not recommended. The SQLite developers do not use them. You should not use them either. If you want a configure script and an automated build, use either the amalgamation tarball or TEA tarball instead of this one. To build from this tarball, hand-edit one of the template Makefiles in the root directory of the tarball and build using your own customized Makefile. } Product {sqlite-preprocessed-VVV.zip} { This ZIP archive contains preprocessed C code for SQLite version VERSION individual source files. The use of this source distribution is not recommended. Use one of the amalgamation packages above unless you have a compelling reason not to. }
$pending_heading
" if {$frag!=""} { eval hd_fragment $frag set frag {} } hd_puts "$file
($size $units)
[string trim $d2]" hd_puts "
(sha1: $sha1sum)
$title
hd_fragment encoding {build product names}

Build Product Names

Beginning with SQLite [version 3.7.4], the names of the build products have changed to be more consistent. (Prior to version 3.7.4, the names of build products were seemingly random.) Build products are named using one of the following templates:

  1. sqlite-product-version.zip
  2. sqlite-product-version.tar.gz
  3. sqlite-product-os-cpu-version.zip
  4. sqlite-product-date.zip

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

Canonical Source Code

The canonical SQLite source code is maintained in three self-synchronizing [http://www.fossil-scm.org/ | 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.

Note that a unix-like development environment, including a recent version of Tcl, is required in order to build from the canonical sources.

http://www.sqlite.org/cgi/src (Dallas)
http://www2.sqlite.org/cgi/src (Atlanta)
http://www3.sqlite.org/cgi/src (Fremont)

The documentation is maintained in separate [http://www.fossil-scm.org/ | Fossil] repositories located at:

http://www.sqlite.org/cgi/docsrc (Dallas)
http://www2.sqlite.org/cgi/docsrc (Atlanta)
http://www3.sqlite.org/cgi/docsrc (Fremont)