Lines Matching +refs:sqlite +refs:handle +refs:common +refs:feature +refs:flags

47 - [sqlite-config.tcl][]: utility code which is too project-specific
69 an `sqlite-` prefix are in [sqlite-config.tcl][]. The others are part
105   flags passed to it (or not), as covered in its docs. This will stick
119   Unlike most functions which deal with `--flags`, this one does not
131 - **`sqlite-add-feature-flag ?-shell? FLAG...`**\  
132   Adds the given feature flag to the CFLAGS which are specific to
134   `-DSQLITE_ENABLE_...`, or similar, flags. If the `-shell` flag is
136   `sqlite-add-shell-opt`. This is a no-op if `FLAG` is not provided or
139 - **`sqlite-add-shell-opt FLAG...`**\  
140   The shell-specific counterpart of `sqlite-add-feature-flag` which
143 - **`sqlite-configure BUILD-NAME {script}`**\  
144   This is where all configure `--flags` are defined for all known
145   build modes ("canonical" or "autoconf"). After processing all flags,
148   common to all build modes. The `auto.def` files are intended to contain
150   `use sqlite-config; sqlite-configure BUILD-NAME {script}`
182 search for an available `tclsh` (under several common names,
207 non-default build flags to enable features which are
260 When the configure script exports flags for consumption by filtered
263 those flags get exported as as C `#define`s to `sqlite_cfg.h`, where
288 In both the legacy Autotools-driven build and common Autosetup usage,
289 feature tests performed by the configure script may amend global flags
296   core set of those flags.
302   in a specific order so that the resulting flags get applied at
305   to collecting build-time flags, the test for `-rpath` had to come
307   implicitly modified global state which broke the zlib feature
308   test. Because the feature tests no longer (intentionally) modify
311 In this build, cases where feature tests modify global state in such a
312 way that it may impact later feature tests are either (A) very
318 results of any given feature test into its own well-defined
321 - The linker flags for zlib are exported from the configure script as
329 It is then up to the Makefile to apply and order the flags however is
333 holds only flags which are either relevant to all targets or, failing
336 set library-level feature toggles, e.g. `-DSQLITE_OMIT_FOO`, in which
379 and its own special handling of `--enable-...` flags makes `--debug`
388 `debug` flag in `auto.def` - duplicated flags are not permitted.
395 customization. Rather than editing `sqlite-config.tcl` for this,
400 `autosetup/sqlite-custom.tcl`.
408 proc sqlite-custom-flags {} {
409   # If any existing --flags require different default values
429 used internally by `sqlite-config.tcl:sqlite-configure`.
435 proc sqlite-custom-handle-flags {} {
450 [sqlite-config.tcl]: /file/autosetup/sqlite-config.tcl