Compare commits

...

3 Commits

Author SHA1 Message Date
shearer 4f8da42b3b Make platform compilation clearer, including the section that applies to both *ix and Windows
Add link to the detailed compilation instructions
Add brief Android section, it seems strange to omit it since Android is the majority use case by numbers

FossilOrigin-Name: 2a71bebfe3139a74736bd87a07b79ccfe73beb2a21d56d3804faa698c3f6edb8
2020-11-03 11:54:42 +00:00
shearer 52a19f3f7c Update for new git-style syntax in Fossil
FossilOrigin-Name: d46b6778b12be39dc101e5decfd9cde7643312d79d4b9af8d75a9bdc8a7481cd
2020-11-03 11:27:41 +00:00
shearer 01685bb277 Add links, especially for the docsrc repo, which is otherwise hard to find
FossilOrigin-Name: e03867e2fbb6bb9c04e13442508c252fd952b397b40aa457cbff09ab1a17d4f7
2020-11-03 11:20:29 +00:00
3 changed files with 35 additions and 1906 deletions
+26 -16
View File
@@ -3,17 +3,18 @@
This repository contains the complete source code for the
[SQLite database engine](https://sqlite.org/). Some test scripts
are also included. However, many other test scripts
and most of the documentation are managed separately.
and [most of the documentation](https://www.sqlite.org/docsrc/doc/trunk/README.md) are managed separately.
## Version Control
SQLite sources are managed using the
[Fossil](https://www.fossil-scm.org/), a distributed version control system
[Fossil SCM](https://www.fossil-scm.org/), a distributed version control system
that was specifically designed and written to support SQLite development.
The [Fossil repository](https://sqlite.org/src/timeline) contains the urtext.
The [Fossil repository](https://sqlite.org/src/timeline) contains the
[urtext](https://en.wiktionary.org/wiki/Urtext).
If you are reading this on GitHub or some other Git repository or service,
then you are looking at a mirror. The names of check-ins and
then you are looking at a read-only mirror. The names of check-ins and
other artifacts in a Git mirror are different from the official
names for those objects. The offical names for check-ins are
found in a footer on the check-in comment for authorized mirrors.
@@ -48,27 +49,26 @@ archives or [SQLite archives](https://sqlite.org/cli.html#sqlar) as follows:
page.
If you do want to use Fossil to check out the source tree,
first install Fossil version 2.0 or later.
first install Fossil version 2.14 or later.
(Source tarballs and precompiled binaries available
[here](https://www.fossil-scm.org/fossil/uv/download.html). Fossil is
a stand-alone program. To install, simply download or build the single
executable file and put that file someplace on your $PATH.)
Then run commands like this:
Then run:
mkdir ~/sqlite
cd ~/sqlite
fossil clone https://www.sqlite.org/src sqlite.fossil
fossil open sqlite.fossil
After setting up a repository using the steps above, you can always
update to the lastest version using:
fossil update trunk ;# latest trunk check-in
which will download the entire sqlite repository into the database file sqlite.fossil,
then check out the local repository into a new directory called "sqlite".
You can always update to the lastest version using:
fossil update trunk ;# latest trunk check-in, or
fossil update release ;# latest official release
Or type "fossil ui" to get a web-based user interface.
## Compiling
## Compiling - Linux and Unix-like Operating Systems
First create a directory in which to place
the build products. It is recommended, but not required, that the
@@ -76,7 +76,7 @@ build directory be separate from the source directory. Cd into the
build directory and then from the build directory run the configure
script found at the root of the source tree. Then run "make".
For example:
For example, if you downloaded a tarball rather than installing Fossil:
tar xzf sqlite.tar.gz ;# Unpack the source tree into "sqlite"
mkdir bld ;# Build will occur in a sibling directory
@@ -94,7 +94,7 @@ script does not work out for you, there is a generic makefile named
can copy and edit to suit your needs. Comments on the generic makefile
show what changes are needed.
## Using MSVC
## Compiling - Using MSVC on Windows
On Windows, all applicable build products can be compiled with MSVC.
First open the command prompt window associated with the desired compiler
@@ -117,10 +117,20 @@ to the "sqlite3.dll" command line above. When debugging into the SQLite
code, adding the "DEBUG=1" argument to one of the above command lines is
recommended.
## Further Information for Windows and Linux/Unix
You may want to refer to the [more detailed compilation instructions](https://www.sqlite.org/howtocompile.html) .
SQLite does not require [Tcl](http://www.tcl.tk/) to run, but a Tcl installation
is required by the makefiles (including those for MSVC). SQLite contains
a lot of generated code and Tcl is used to do much of that code generation.
## Compiling - Android
The [Android version of SQLite](https://sqlite.org/android/doc/trunk/www/install.wiki) is in
its own repository. You will need the Android SDK and NDK, and to follow the
[Android-specific build instructions](https://sqlite.org/android/doc/trunk/www/install.wiki).
## Source Code Tour
Most of the core source files are in the **src/** subdirectory. The
+8 -1889
View File
File diff suppressed because it is too large Load Diff
+1 -1
View File
@@ -1 +1 @@
6646d7898ca1d2f71ec906d9613fbfc5c59c6cf05f053529e6e32ab826d1cb78
2a71bebfe3139a74736bd87a07b79ccfe73beb2a21d56d3804faa698c3f6edb8