[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43754: [PATCH] configure help message of --with-json
From: |
Lars Ingebrigtsen |
Subject: |
bug#43754: [PATCH] configure help message of --with-json |
Date: |
Fri, 02 Oct 2020 16:28:38 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
> Any reason why we use OPTION_DEFAULT_IFAVAILABLE for json, and not
> OPTION_DEFAULT_ON? How is it different from libpng or liblcms2 or
> libgnutls?
I wonder whether it's because of this:
case $with_gnutls,$HAVE_GNUTLS in
no,* | ifavailable,* | *,yes) ;;
*) MISSING="$MISSING gnutls"
WITH_IFAVAILABLE="$WITH_IFAVAILABLE --with-gnutls=ifavailable";;
esac
case $with_json,$HAVE_JSON in
no,* | ifavailable,* | *,yes) ;;
*) MISSING="$MISSING json"
WITH_IFAVAILABLE="$WITH_IFAVAILABLE --with-json=ifavailable";;
esac
But if I understand autoconf (and I do not), that shouldn't really
"spread" to the OPTION_DEFAULT_ stuff, should it?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no