Lines Matching +refs:proj +refs:define +refs:for +refs:opt
4 This document provides some tips and reminders for the SQLite
17 - ***[Patching Autosetup for Project-local changes](#patching)***
41 - [proj.tcl][]: project-agnostic utility code for autosetup-driven
48 for `proj.tcl`. We split this out of `auto.def` so that it can be
50 - [auto.def][]: the primary driver for the `./configure` process.
54 - [autoconf/auto.def][]: the main driver script for the "autoconf"
68 those with `proj-` prefix can be found in [proj.tcl][] and those with
77 check for `${filename}.exe` on Windows platforms. However, on such
85 - **`proj-get-env VAR ?default?`**\
87 look for a file named `./.env-$VAR` and, if found, return its
89 local preferences for the default `CFLAGS`.\
94 - **`proj-fatal msg`**\
98 - **`proj-if-opt-truthy flag thenScript ?elseScript?`**\
102 - **`proj-indented-notice ?-error? ?-notice? msg`**\
106 out starkly from normal output and is intended to be used only for
109 - **`proj-opt-truthy flag`**\
113 - **`proj-opt-was-provided FLAG`**\
116 `--with-readline` was provided or whether we're searching for
123 - **`proj-val-truthy value`**\
124 Returns 1 if `$value` is "truthy," See `proj-opt-truthy` for the definition
127 - **`proj-warn msg`**\
136 `sqlite-add-shell-opt`. This is a no-op if `FLAG` is not provided or
139 - **`sqlite-add-shell-opt FLAG...`**\
144 This is where all configure `--flags` are defined for all known
156 used to generate warnings between a "checking for..." message and
182 search for an available `tclsh` (under several common names,
185 system-installed TCL for running the configure script. Once it finds
202 before looking for a system-level `tclsh`. Be aware, though, that
206 which gets built for code-generation purposes. The latter requires
209 This means, for example, that the configure script and its utility
211 TCL-only implementation of `[file-normalize]` (note the dash) for
225 close enough to `-translation lf` for our purposes. When working
231 [](/info/61f18c96183867fe) for a workaround.
247 This section describes the motivations for the most glaring of the
255 `UPPER_UNDERSCORE` form for makefile variables. This build, however,
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
270 into into `X.y` form for consumption by [Makefile.in][] and
282 of taste, for which there is no accounting.)
291 appropriate for a makefile which builds a single deliverable, but less
292 so for makefiles which produce multiple deliverables. Drawbacks of
305 to collecting build-time flags, the test for `-rpath` had to come
306 _after_ the test for zlib because the results of the `-rpath` test
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
325 needed for including `libreadline`, `libedit`, or `linenoise`, and
341 [^as-cflags]: But see this article for a detailed discussion of how
371 for the change described in the following section**, test the
375 Patching Autosetup for Project-local Changes
378 Autosetup reserves the flag name **`--debug`** for its own purposes,
380 an alias for `--enable-debug`. As this project has a long history of
395 customization. Rather than editing `sqlite-config.tcl` for this,
431 Next, define:
449 [proj.tcl]: /file/autosetup/proj.tcl