I've got to say, the distinction between --with and --enable, no matter how thoretically pure, in practice seems extremely fuzzy. Quoting Neil Schemenauer quoting the autoconf docs (http://mail.python.org/pipermail/python-dev/2001-January/011938.html): | If a software package has optional compile-time features, the | user can give `configure' command line options to specify | whether to compile them. The options have one of these forms: | | --enable-FEATURE[=ARG] | --disable-FEATURE | | Some packages require, or can optionally use, other software | packages which are already installed. The user can give | `configure' command line options to specify which such | external software to use. The options have one of these | forms: | | --with-package[=ARG] | --without-package Now, for example, should it be --with-ipv6 or --enable-ipv6? I would think --with, since this is clearly depending on optional external software. Yet, it is one of the few configure options that use --enable. I am seriously considering standardizing on --with, ignoring the autoconf docs. Given how vague the distinction is, I'm sure most users will find the distinction completely arbitrary even if we applied the rules correctly. They would be better served with a consistent rule they can remember, like "always use --with/--without". --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4