+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)])
+])
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 :)
The problem is that --without means "exlusion", and you print
"inclusion", for which the "yes" and "no" states are in proper order,
but for "exclusion", they are swaped. All would be fine, if you would
have used --with-internals, but since you used --without-internals,
everything should be worded the other way round. Actually configure
checks for the existance of the internals exclusion parameter, so the
message should be worded accordingly for which the states should be
swapped.
Goba
OK!
Sorry for the confusion,
Nuno
