Lines Matching +refs:sqlite +refs:configure
32 $ ./configure --reference | less
47 - [sqlite-config.tcl][]: utility code which is too project-specific
50 - [auto.def][]: the primary driver for the `./configure` process.
51 When we talk about "the configure script," we're technically
55 bundle's configure script. It is essentially a slightly trimmed-down
69 an `sqlite-` prefix are in [sqlite-config.tcl][]. The others are part
82 KEY=VALUE passed to the configure script or (2) the system's
114 Returns 1 if `--FLAG` was explicitly provided to configure,
131 - **`sqlite-add-feature-flag ?-shell? FLAG...`**\
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
150 `use sqlite-config; sqlite-configure BUILD-NAME {script}`
169 It is important that any TCL files used by the configure process and
178 When [`./configure`](/file/configure) is run, it goes through a
185 system-installed TCL for running the configure script. Once it finds
190 There are two simple ways to ensure that running of the configure
192 approach provides equally high assurances about configure script
196 case, the configure process will fall back to building the in-tree
201 With that in place, the configure script will prefer to use that
209 This means, for example, that the configure script and its utility
212 portable use in the configure script. Contrariwise, code-generation
260 When the configure script exports flags for consumption by filtered
289 feature tests performed by the configure script may amend global flags
299 performed outside the immediate visibility of the configure script's
301 - It can force the maintainers of the configure script to place tests
316 This tree's [configure script][auto.def], [utility APIs][proj.tcl],
321 - The linker flags for zlib are exported from the configure script as
332 At the end of the configure script, the global `CFLAGS` _ideally_
335 clients frequently pass custom `CFLAGS` to `./configure` or `make` to
372 configure process, and check it in.
387 `./configure` will fail loudly because of the declaration of the
394 Certain vendor-specific branches require slight configure script
395 customization. Rather than editing `sqlite-config.tcl` for this,
400 `autosetup/sqlite-custom.tcl`.
408 proc sqlite-custom-flags {} {
429 used internally by `sqlite-config.tcl:sqlite-configure`.
435 proc sqlite-custom-handle-flags {} {
441 configure process, before any filtered files are generated but after
450 [sqlite-config.tcl]: /file/autosetup/sqlite-config.tcl