Rework of #975, which I'm taking over with the permission of @elichai.
See commit messages for some more rationale.
These are set automatically by autoconf [1], and this has been the
case in at least since 2.60, which is our minimum supported version.
[1] https://www.gnu.org/software/autoconf/manual/autoconf-2.70/html_node/Package-Options.html
[2] https://www.gnu.org/software/autoconf/manual/autoconf-2.60/html_node/Package-Options.html
I was wondering whether we should disable the benchmarks by default. I think normal users won't need them and I suspect these were more interesting in the early days of the library.
The benchmarks were actually disabled at some point by default, which led to a lot of wasted time for me because I forgot to compile benchmarks, and then ended up running with an old bench binary...
42 | +dnl SECP_SET_DEFAULT(VAR, default, default-dev-mode) 43 | +dnl Set VAR to default or default-dev-mode, depending on whether dev mode is enabled 44 | +AC_DEFUN([SECP_SET_DEFAULT], [ 45 | + if test "${enable_dev_mode+set}" != set; then 46 | + AC_MSG_ERROR([[Set enable_dev_mode before calling SECP_SET_DEFAULT]]) 47 | + fi
nit: trailing whitespace
fixed
ACK mod nit
This is useful.
Co-authored-by: Elichai Turkel <elichai.turkel@gmail.com>
ACK e0838d663deba5a9663a0ad02bd7e4c563325c4d
@elichai Want to review this?
tACK e0838d663deba5a9663a0ad02bd7e4c563325c4d
Tested that this is actually hidden, that it enables all the modules as expected, and that it supports disabling specific modules