To address the need that instigated the build problem <u>[described here](https://sqlite.org/forum/forumpost/d473394316)</u>, we will soon implement a new, build-time-visible feature. Comments, for or against, or improvement suggestions, are welcome. The way it will work will be to allow one or both of the following:<code> \<compile\> -DSQLITE_CUSTOM_INC=my_options.h ... </code>or<code> \<compile\> -DSQLITE_CUSTOM_INCQ="my_options.h" ... </code>. The effect will be to #include the defined file at a point in the translation unit no later than where the published compilation options take effect, including effects upon built-in option discovery. This feature will exist for both the SQLite library (amalgamation) and the SQLite CLI shell, using the same macro name. Support for passing this through the Makefile (or equivalent) will be put in place, so that existing ways of adding options upon make invocation still work. (Any collisions between those mechanisms will be on users.) Please make objections or worthy suggestions known before the next release.