Lines Matching refs:to
12 that was specifically designed and written to support SQLite development.
24 If you pulled your SQLite source code from a secondary source and want to
25 verify its integrity, there are hints on how to do that in the
30 If you do not want to use Fossil, you can download tarballs or ZIP
46 to locate the check-in desired, click on its information page link,
50 If you do want to use Fossil to check out the source tree,
64 update to the latest version using:
69 Or type "fossil ui" to get a web-based user interface.
73 First create a directory in which to place
83 cd bld ;# Change to the build directory
94 can copy and edit to suit your needs. Comments on the generic makefile
102 with the provided "Makefile.msc" to build one of the supported targets.
115 line. For example, to build for WinRT, simply add "FOR_WINRT=1" argument
116 to the "sqlite3.dll" command line above. When debugging into the SQLite
117 code, adding the "DEBUG=1" argument to one of the above command lines is
120 SQLite does not require [Tcl](http://www.tcl.tk/) to run, but a Tcl installation
122 a lot of generated code and Tcl is used to do much of that code generation.
127 **src/** folder also contains files used to build the "testfixture" test
136 extension and only later escaped to the wild as an independent library.)
159 fill it with all the source files needed to build SQLite, both
166 and is used to generate the SQLITE\_SOURCE\_ID macro. The VERSION file
170 used to generate much of the SQLite API documentation. The Tcl scripts
171 used to generate that documentation are in a separate source repository.
182 corresponding to opcodes in the "VDBE" virtual machine. The opcodes.h
185 A second Tcl script, ./mkopcodec.tcl, then scans opcodes.h to generate
187 opcode-number to opcode-name that is used for EXPLAIN output.
194 The **pragma.h** header file contains various definitions used to parse
196 script **tool/mkpragmatab.tcl**. If you want to add a new PRAGMA, edit
197 the **tool/mkpragmatab.tcl** file to insert the information needed by the
198 parser for your new PRAGMA, then run the script to regenerate the
208 to perform more cross-procedure analysis and generate better code. SQLite
215 tool/mksqlite3c.tcl script is run to copy them all together in just the
219 debuggers (most notably MSVC) are unable to deal with files longer than 64K
221 can be run on the amalgamation to break it up into a single small C file
233 (helping to understand how SQLite works include the
241 for small size and high performance. And optimizations tend to result in
243 implementation. It will not be the easiest library in the world to hack.
247 * **sqlite.h.in** - This file defines the public interface to the SQLite
248 library. Readers will need to be familiar with this interface before
249 trying to understand how the library works internally.
252 used internally by SQLite. In addition to "sqliteInt.h", some
256 to parse SQL statements, and the actions that are taken at each step
261 begin with "vdbe". The VDBE has access to the vdbeInt.h header file
267 virtual machine code to run queries efficiently. This file is
272 storage engine used by SQLite. The interface to the rest of the system
274 used internally by btree.c and not published to the rest of the system.
296 test/ folder to validate the core SQLite code. The testfixture program