+dnl {{{ disable Internals documentation
+
+AC_MSG_CHECKING(for internals docs inclusion)
+
+AC_ARG_WITH(internals,
+[ --without-internals disable internals docs inclusion],
+[
+ INTERNALS_INCL_BEGIN="<!--"
+ INTERNALS_INCL_END="-->"
+ AC_MSG_RESULT([no])
+],[
+ INTERNALS_INCL_BEGIN=""
+ INTERNALS_INCL_END=""
+ AC_MSG_RESULT([yes (default)])
+])
You mean the other way round! :) Either name the parameter
--with-internals, or swap the order of the variable settings.
--without-internals=yes should mean the addition of the comments, and
should not be the default.
Goba
I've tested and it worked..
'./configure' does include the internals docs
while './configure --without-internals' doesn't
Nuno
But the code still does not make sense... It might work, but it prints
(yes in your first example, and no in your second, which is
contradictory to the intended result :) At least I guess.
Goba
Well.. no :)
'./configure' prints:
"checking for internals docs inclusion... yes (default)"
That means that the intenals docs are included and the comments aren't
inserted.
'./configure --without-internals' prints:
"checking for internals docs inclusion... no"
Here the comments are included, thus disabling those docs.
I don't know anything about autoconf, I've just copy-paste that from an
example, so it might not be correct, but it works :)
Nuno