Lines Matching refs:file

20 The official check-in name can also be seen in the `manifest.uuid` file
55 executable file and put that file someplace on your $PATH.)
86         make sqlite3.c           ;#  Build the "amalgamation" source file
130 The **src/** also contains the "shell.c" file
133 the "tclsqlite.c" file which implements the
146 smaller, single-file extensions, such as a REGEXP operator.
162 The SQLite interface is defined by the **sqlite3.h** header file, which is
165 The manifest.uuid file contains the SHA3 hash of the particular check-in
166 and is used to generate the SQLITE\_SOURCE\_ID macro.  The VERSION file
169 at just the right spots. Note that comment text in the sqlite3.h file is
174 the src/parse.y file.  The conversion of "parse.y" into "parse.c" is done
176 for lemon is at tool/lemon.c.  Lemon uses the tool/lempar.c file as a
178 Lemon also generates the **parse.h** header file, at the same time it
181 The **opcodes.h** header file contains macros that define the numbers
183 file is generated by scanning the src/vdbe.c source file.  The
186 the **opcodes.c** source file, which contains a reverse mapping from
189 The **keywordhash.h** header file contains the definition of a hash table
191 the numeric codes used by the parse.c parser.  The keywordhash.h file is
194 The **pragma.h** header file contains various definitions used to parse
197 the **tool/mkpragmatab.tcl** file to insert the information needed by the
199 **pragma.h** header file.
204 and automatically-generated) can be combined into a single big source file
207 source code files into a single big source code file allows the C compiler
218 The amalgamation source file is more than 200K lines long.  Some symbolic
221 can be run on the amalgamation to break it up into a single small C file
226 individual source file exceeds 32K lines in length.
234 [file format](http://www.sqlite.org/fileformat2.html) description,
247   *  **sqlite.h.in** - This file defines the public interface to the SQLite
251   *  **sqliteInt.h** - this header file defines many of the data objects
255   *  **parse.y** - This file describes the LALR(1) grammar that SQLite uses
259   *  **vdbe.c** - This file implements the virtual machine that runs
261      begin with "vdbe".  The VDBE has access to the vdbeInt.h header file
265   *  **where.c** - This file (together with its helper files named
267      virtual machine code to run queries efficiently.  This file is
269      header file, whereInt.h, that defines data objects used internally.
271   *  **btree.c** - This file contains the implementation of the B-Tree
276   *  **pager.c** - This file contains the "pager" implementation, the
277      module that implements transactions.  The "pager.h" header file
284   *  **shell.c.in** - This file is not part of the core SQLite library.  This
285      is the file that, when linked against sqlite3.a, generates the
286      "sqlite3.exe" command-line shell.  The "shell.c.in" file is transformed
289   *  **tclsqlite.c** - This file implements the Tcl bindings for SQLite.  It
300   *  **ext/misc/json1.c** - This file implements the various JSON functions
309 The `manifest` file at the root directory of the source tree
311 older files) for every source file in the repository.
313 SHA3-256 hash of the `manifest` file itself, possibly with the
314 last line of that file omitted if the last line begins with
316 The `manifest.uuid` file should contain the SHA3-256 hash of the
317 `manifest` file. If all of the above hash comparisons are correct, then
320 The format of the `manifest` file should be mostly self-explanatory, but