Lines Matching +refs:sqlite +refs:add +refs:shell +refs:opt
47 - [sqlite-config.tcl][]: utility code which is too project-specific
69 an `sqlite-` prefix are in [sqlite-config.tcl][]. The others are part
98 - **`proj-if-opt-truthy flag thenScript ?elseScript?`**\
109 - **`proj-opt-truthy flag`**\
113 - **`proj-opt-was-provided FLAG`**\
124 Returns 1 if `$value` is "truthy," See `proj-opt-truthy` for the definition
131 - **`sqlite-add-feature-flag ?-shell? FLAG...`**\
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
141 only adds the given flag(s) to the CLI-shell-specific CFLAGS.
143 - **`sqlite-configure BUILD-NAME {script}`**\
150 `use sqlite-config; sqlite-configure BUILD-NAME {script}`
181 TCL shell](/file/autosetup/autosetup-find-tclsh). That will first
186 (or builds) a TCL shell, it then runs [a sanity test to ensure that
187 the shell is suitable](/file/autosetup/autosetup-test-tclsh) before
395 customization. Rather than editing `sqlite-config.tcl` for this,
400 `autosetup/sqlite-custom.tcl`.
404 If flag customization is required, add:
408 proc sqlite-custom-flags {} {
429 used internally by `sqlite-config.tcl:sqlite-configure`.
435 proc sqlite-custom-handle-flags {} {
450 [sqlite-config.tcl]: /file/autosetup/sqlite-config.tcl