Skip to content

Commit 661f12a

Browse files
kobboimurraycu
authored andcommitted
Make --disable-benchmark work
Currently, when calling ./configure, the possible outcomes of the enable_benchmark variable are: ./configure -> "" ./configure --enable-benchmark -> "yes" ./configure --enable-benchmark=yes -> "yes" ./configure --enable-benchmark=no -> "yes" ./configure --enable-benchmark=hello -> "yes" ./configure --disable-benchmark -> "yes" With this commit, those values become ./configure -> "" ./configure --enable-benchmark -> "yes" ./configure --enable-benchmark=yes -> "yes" ./configure --enable-benchmark=no -> "no" ./configure --enable-benchmark=hello -> "hello" ./configure --disable-benchmark -> "no" Note that enable_benchmark is currently only being checked for being "yes" or not. Bug #774732
1 parent 83f1e2f commit 661f12a

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

configure.ac

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -69,8 +69,7 @@ MM_ARG_ENABLE_WARNINGS([SIGC_WXXFLAGS],
6969
MM_ARG_DISABLE_DEPRECATED_API([SIGCXX])
7070

7171
AC_ARG_ENABLE(benchmark,
72-
AS_HELP_STRING([--enable-benchmark=yes|no]),
73-
[enable_benchmark=yes]
72+
AS_HELP_STRING([--enable-benchmark=yes|no])
7473
)
7574

7675
AM_CONDITIONAL([SIGC_BUILD_BENCHMARK], [test "x$enable_benchmark" = xyes])

0 commit comments

Comments
 (0)