@@ -72,75 +72,75 @@ in ./autosetup](/dir/autosetup).
7272
7373In (mostly) alphabetical order:
7474
75- - ** ` file-isexec filename ` ** \
75+ - ** ` file-isexec filename ` ** \
7676 Should be used in place of ` [file executable] ` , as it will also
7777 check for ` ${filename}.exe ` on Windows platforms. However, on such
7878 platforms it also assumes that _ any_ existing file is executable.
7979
80- - ** ` get-env VAR ?default? ` ** \
80+ - ** ` get-env VAR ?default? ` ** \
8181 Will fetch an "environment variable" from the first of either: (1) a
8282 KEY=VALUE passed to the configure script or (2) the system's
8383 environment variables. Not to be confused with ` getenv ` , which only
8484 does the latter and is rarely, if ever, useful in this tree.
85- - ** ` proj-get-env VAR ?default? ` ** \
85+ - ** ` proj-get-env VAR ?default? ` ** \
8686 Works like ` get-env ` but will, if that function finds no match,
8787 look for a file named ` ./.env-$VAR ` and, if found, return its
8888 trimmed contents. This can be used, e.g., to set a developer's
89- local preferences for the default ` CFLAGS ` .\
89+ local preferences for the default ` CFLAGS ` .\
9090 Tip: adding ` -O0 ` to ` .env-CFLAGS ` reduces rebuild times
9191 considerably at the cost of performance in ` make devtest ` and the
9292 like.
9393
94- - ** ` proj-fatal msg ` ** \
94+ - ** ` proj-fatal msg ` ** \
9595 Emits ` $msg ` to stderr and exits with non-zero. Its differences from
9696 autosetup's ` user-error ` are purely cosmetic.
9797
98- - ** ` proj-if-opt-truthy flag thenScript ?elseScript? ` ** \
98+ - ** ` proj-if-opt-truthy flag thenScript ?elseScript? ` ** \
9999 Evals ` thenScript ` if the given ` --flag ` is truthy, else it
100100 evals the optional ` elseScript ` .
101101
102- - ** ` proj-indented-notice ?-error? ?-notice? msg ` ** \
102+ - ** ` proj-indented-notice ?-error? ?-notice? msg ` ** \
103103 Breaks its ` msg ` argument into lines, trims them, and emits them
104104 with consistent indentation. Exactly how it emits depends on the
105105 flags passed to it (or not), as covered in its docs. This will stick
106106 out starkly from normal output and is intended to be used only for
107107 important notices.
108108
109- - ** ` proj-opt-truthy flag ` ** \
109+ - ** ` proj-opt-truthy flag ` ** \
110110 Returns 1 if ` --flag ` 's value is "truthy," i.e. one of (1, on,
111111 enabled, yes, true).
112112
113- - ** ` proj-opt-was-provided FLAG ` ** \
113+ - ** ` proj-opt-was-provided FLAG ` ** \
114114 Returns 1 if ` --FLAG ` was explicitly provided to configure,
115115 else 0. This distinction can be used to determine, e.g., whether
116116 ` --with-readline ` was provided or whether we're searching for
117117 readline by default. In the former case, failure to find it should
118- be treated as fatal, where in the latter case it's not.\
118+ be treated as fatal, where in the latter case it's not.\
119119 Unlike most functions which deal with ` --flags ` , this one does not
120120 validate that ` $FLAG ` is a registered flag so will not fail fatally
121121 if ` $FLAG ` is not registered as an Autosetup option.
122122
123- - ** ` proj-val-truthy value ` ** \
123+ - ** ` proj-val-truthy value ` ** \
124124 Returns 1 if ` $value ` is "truthy," See ` proj-opt-truthy ` for the definition
125125 of "truthy."
126126
127- - ** ` proj-warn msg ` ** \
127+ - ** ` proj-warn msg ` ** \
128128 Emits ` $msg ` to stderr. Closely-related is autosetup's ` user-notice `
129129 (described below).
130130
131- - ** ` sqlite-add-feature-flag ?-shell? FLAG... ` ** \
131+ - ** ` sqlite-add-feature-flag ?-shell? FLAG... ` ** \
132132 Adds the given feature flag to the CFLAGS which are specific to
133133 building libsqlite3. It's intended to be passed one or more
134134 ` -DSQLITE_ENABLE_... ` , or similar, flags. If the ` -shell ` flag is
135135 used then it also passes its arguments to
136136 ` sqlite-add-shell-opt ` . This is a no-op if ` FLAG ` is not provided or
137137 is empty.
138138
139- - ** ` sqlite-add-shell-opt FLAG... ` ** \
139+ - ** ` sqlite-add-shell-opt FLAG... ` ** \
140140 The shell-specific counterpart of ` sqlite-add-feature-flag ` which
141141 only adds the given flag(s) to the CLI-shell-specific CFLAGS.
142142
143- - ** ` sqlite-configure BUILD-NAME {script} ` ** \
143+ - ** ` sqlite-configure BUILD-NAME {script} ` ** \
144144 This is where all configure ` --flags ` are defined for all known
145145 build modes ("canonical" or "autoconf"). After processing all flags,
146146 this function runs ` $script ` , which contains the build-mode-specific
@@ -149,7 +149,7 @@ In (mostly) alphabetical order:
149149 exactly two commands:
150150 ` use sqlite-config; sqlite-configure BUILD-NAME {script} `
151151
152- - ** ` user-notice msg ` ** \
152+ - ** ` user-notice msg ` ** \
153153 Queues ` $msg ` to be sent to stderr, but does not emit it until
154154 either ` show-notices ` is called or the next time autosetup would
155155 output something (it internally calls ` show-notices ` ). This can be
@@ -196,8 +196,8 @@ compatibility across TCL implementations:
196196 case, the configure process will fall back to building the in-tree
197197 copy of JimTCL.
198198
199- 2 . Manually build ` ./jimsh0 ` in the top of the checkout with:\
200- ` cc -o jimsh0 autosetup/jimsh0.c ` \
199+ 2 . Manually build ` ./jimsh0 ` in the top of the checkout with:\
200+ ` cc -o jimsh0 autosetup/jimsh0.c ` \
201201 With that in place, the configure script will prefer to use that
202202 before looking for a system-level ` tclsh ` . Be aware, though, that
203203 ` make distclean ` will remove that file.
@@ -300,7 +300,7 @@ that approach include:
300300 maintainer.
301301- It can force the maintainers of the configure script to place tests
302302 in a specific order so that the resulting flags get applied at
303- the correct time and/or in the correct order.\
303+ the correct time and/or in the correct order.\
304304 (A real-life example: before the approach described below was taken
305305 to collecting build-time flags, the test for ` -rpath ` had to come
306306 _ after_ the test for zlib because the results of the ` -rpath ` test
@@ -380,8 +380,9 @@ and its own special handling of `--enable-...` flags makes `--debug`
380380an alias for ` --enable-debug ` . As this project has a long history of
381381using ` --enable-debug ` , we patch autosetup to use the name
382382` --autosetup-debug ` in place of ` --debug ` . That requires (as of this
383- writing) four small edits in [ ] ( /file/autosetup/autosetup ) , as
384- demonstrated in [ check-in 3296c8d3] ( /info/3296c8d3 ) .
383+ writing) four small edits in
384+ [ /autosetup/autosetup] ( /file/autosetup/autosetup ) , as demonstrated in
385+ [ check-in 3296c8d3] ( /info/3296c8d3 ) .
385386
386387If autosetup is upgraded and this patch is _ not_ applied the invoking
387388` ./configure ` will fail loudly because of the declaration of the
@@ -426,7 +427,7 @@ proc sqlite-custom-flags {} {
426427```
427428
428429That function must return either an empty string or a list in the form
429- used internally by ` sqlite-config.tcl: sqlite-configure ` .
430+ used internally by [ sqlite-config.tcl] [ ] 's ` sqlite-configure ` .
430431
431432Next, define:
432433
0 commit comments