Lines Matching +refs:sqlite +refs:check +refs:tcl
41 - [proj.tcl][]: project-agnostic utility code for autosetup-driven
47 - [sqlite-config.tcl][]: utility code which is too project-specific
48 for `proj.tcl`. We split this out of `auto.def` so that it can be
68 those with `proj-` prefix can be found in [proj.tcl][] and those with
69 an `sqlite-` prefix are in [sqlite-config.tcl][]. The others are part
77 check for `${filename}.exe` on Windows platforms. However, on such
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}`**\
150 `use sqlite-config; sqlite-configure BUILD-NAME {script}`
316 This tree's [configure script][auto.def], [utility APIs][proj.tcl],
372 configure process, and check it in.
384 demonstrated in [check-in 3296c8d3](/info/3296c8d3).
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 {} {
449 [proj.tcl]: /file/autosetup/proj.tcl
450 [sqlite-config.tcl]: /file/autosetup/sqlite-config.tcl
453 [JimTCL]: https://jim.tcl.tk