Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix typos in the compile.html document. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
32b04c8243f8829435bba70a2dafbc07 |
| User & Date: | drh 2013-04-30 11:51:45 |
Context
|
2013-04-30
| ||
| 16:49 | Add the Next Generation Query Planner document. check-in: 74fbc7b392 user: drh tags: trunk | |
| 11:51 | Fix typos in the compile.html document. check-in: 32b04c8243 user: drh tags: trunk | |
|
2013-04-27
| ||
| 18:31 | More documentation tweaks. Add two new entries to the "limits" page. check-in: 8da1a575d7 user: drh tags: trunk | |
Changes
Changes to pages/compile.in.
146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 ... 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 .... 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 |
COMPILE_OPTION {SQLITE_MAX_MMAP_SIZE=<i>N</i>} {
This macro sets a hard upper bound on the amount of address space that
can be used by any single database for memory-mapped I/O.
Setting this value to 0 completely disables memory-mapped I/O and
causes logic associated with memory-mapped I/O to be omitted from the
build. This option does change the default memory-mapped I/O address
space size (set by [SQLITE_DEFAULT_MMAP_SIZE] or
sqlite3_config([SQLITE_CONFIG_MMAP_SIZE])) or the
run-time memory-mapped I/O address space size (set by
sqlite3_file_control([SQLITE_FCNTL_MMAP_SIZE])) or
[PRAGMA mmap_size]) as long as those other settings are less than the
maximum value defined here.
}
COMPILE_OPTION {SQLITE_MAX_SCHEMA_RETRY=<i>N</i>} {
Whenever the database schema changes, prepared statements are automatically
reprepared to accommodate the new schema. There is a race condition here
................................................................................
<tcl>
hd_fragment "omitfeatures"
hd_keywords "omitfeatures"
</tcl>
<h2>1.6 Options To Omit Features</h2>
<p>The following options can used to
[relfootprint | reduce the size of the compiled library]
by omitting unused features. This is probably only useful
in embedded systems where space is especially tight, as even with all
features included the SQLite library is relatively small. Don't forget
to tell your compiler to optimize for binary size! (the -Os option if
using GCC). Telling your compiler to optimize for size usually has
a much larger impact on library footprint than employing any of these
................................................................................
}
COMPILE_OPTION {SQLITE_OMIT_WAL} {
This option omits the "[write-ahead log]" (a.k.a. "[WAL]") capability.
}
COMPILE_OPTION {SQLITE_OMIT_WSD} {
This options builds a version of the SQLite library that contains no
Writable Static Data (WSD). WSD is global variables and/or static
variables. Some platforms do not support WSD, and this option is necessary
in order for SQLite to work those platforms.
Unlike other OMIT options which make the SQLite library smaller,
this option actually increases the size of SQLite and makes it run
a little slower. Only use this option if SQLite is being built for an
|
| | | | |
146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 ... 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 .... 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 |
COMPILE_OPTION {SQLITE_MAX_MMAP_SIZE=<i>N</i>} {
This macro sets a hard upper bound on the amount of address space that
can be used by any single database for memory-mapped I/O.
Setting this value to 0 completely disables memory-mapped I/O and
causes logic associated with memory-mapped I/O to be omitted from the
build. This option does change the default memory-mapped I/O address
space size (set by [SQLITE_DEFAULT_MMAP_SIZE] or
sqlite3_config([SQLITE_CONFIG_MMAP_SIZE]) or the
run-time memory-mapped I/O address space size (set by
sqlite3_file_control([SQLITE_FCNTL_MMAP_SIZE]) or
[PRAGMA mmap_size]) as long as those other settings are less than the
maximum value defined here.
}
COMPILE_OPTION {SQLITE_MAX_SCHEMA_RETRY=<i>N</i>} {
Whenever the database schema changes, prepared statements are automatically
reprepared to accommodate the new schema. There is a race condition here
................................................................................
<tcl>
hd_fragment "omitfeatures"
hd_keywords "omitfeatures"
</tcl>
<h2>1.6 Options To Omit Features</h2>
<p>The following options can be used to
[relfootprint | reduce the size of the compiled library]
by omitting unused features. This is probably only useful
in embedded systems where space is especially tight, as even with all
features included the SQLite library is relatively small. Don't forget
to tell your compiler to optimize for binary size! (the -Os option if
using GCC). Telling your compiler to optimize for size usually has
a much larger impact on library footprint than employing any of these
................................................................................
}
COMPILE_OPTION {SQLITE_OMIT_WAL} {
This option omits the "[write-ahead log]" (a.k.a. "[WAL]") capability.
}
COMPILE_OPTION {SQLITE_OMIT_WSD} {
This option builds a version of the SQLite library that contains no
Writable Static Data (WSD). WSD is global variables and/or static
variables. Some platforms do not support WSD, and this option is necessary
in order for SQLite to work those platforms.
Unlike other OMIT options which make the SQLite library smaller,
this option actually increases the size of SQLite and makes it run
a little slower. Only use this option if SQLite is being built for an
|