[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Best-practice for (not?) re-using/caching computed --with options

From: Simon Sobisch
Subject: Best-practice for (not?) re-using/caching computed --with options
Date: Mon, 27 Feb 2023 08:46:20 +0100
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0

Commonly (?) --with-foo is used in the following way:

--without-foo: disable foo, don't do any checks for it
--with-foo=bar check for foo using bar, if it doesn't work, error
--with-foo=baz check for foo using baz, if it doesn't work, error
--with-foo=check: check if foo works with bar or baz,
               if it doesn't work, disable
not specified: same as with-foo=check
--with-foo:    same as specified, but if it doesn't work, error

This matches the documentation for AC_ARG_WITH

All of --with-foo, --with-foo=bar and --without-foo are re-used (when configure is re-run by make, then those will be used, again) and the test for them may _should_ be cached (I _guess_ this is a best practive but I did not found that in the documentation).
Please correct me if anything so far is wrong.

But when re-run by make without being specified on the original configure command line, then the check for foo would be re-run, which could lead to the program being configured different then before (for example because a system header was added/removed).

I do search for a "best practice" solution - should the check in configure for foo cache its result as-if --with-for / --without-foo was specified by the user?

Would it be more reasonable to not do any caching if --with-foo=check is implied, so the check is always done? Should this be different if --with-foo=check was explicit specified (which I _guess_ could be test with some _set variable)?

Is there an option to "add" to the configure options that are used for re-running the configure script?

Thanks for any pointers,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]