summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAleksander Morgado <aleksander@aleksander.es>2014-09-15 08:56:36 (GMT)
committerAleksander Morgado <aleksander@aleksander.es>2014-09-15 09:00:57 (GMT)
commit8718ed53bee53519fb11f313dfbe55be527f6d76 (patch)
treeae59d3ae55b1fdf30b4536d2a9f324dac8338c40
parent340ff7dce3517b2b476a408572794e5206f43bac (diff)
build: remove --with-newest-qmi-commands configure optionHEADmaster
We don't want people to use the logic enabled by this switch, so remove it from configure to avoid confusions. Developers can still enable the related code by defining WITH_NEWEST_QMI_COMMANDS via CFLAGS; e.g.: $ NOCONFIGURE=1 ./autogen.sh $ ./configure CFLAGS="-DWITH_NEWEST_QMI_COMMANDS"
-rw-r--r--configure.ac20
1 files changed, 0 insertions, 20 deletions
diff --git a/configure.ac b/configure.ac
index 4515f3f..c0064d2 100644
--- a/configure.ac
+++ b/configure.ac
@@ -236,25 +236,6 @@ case $with_qmi in
;;
esac
-dnl
-dnl Newest QMI commands
-dnl
-AC_ARG_WITH(newest_qmi_commands, AS_HELP_STRING([--with-newest-qmi-commands], [Try to avoid deprecated QMI commands]))
-AM_CONDITIONAL(WITH_NEWEST_QMI_COMMANDS, test "x$with_newest_qmi_commands" = "xyes")
-case $with_newest_qmi_commands in
- yes)
- if test "x$with_qmi" = "xno" ; then
- AC_ERROR([Cannot enable newest QMI commands if QMI support is disabled])
- fi
-
- AC_DEFINE(WITH_NEWEST_QMI_COMMANDS, 1, [Define if we enable new QMI commands support])
- with_newest_qmi_commands=yes
- ;;
- *)
- with_newest_qmi_commands=no
- ;;
-esac
-
NM_COMPILER_WARNINGS
@@ -332,5 +313,4 @@ echo "
Documentation: ${enable_gtk_doc}
MBIM support: ${with_mbim}
QMI support: ${with_qmi}
- Newest QMI commands: ${with_newest_qmi_commands}
"