You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
53 lines
2.2 KiB
53 lines
2.2 KiB
2 years ago
|
dnl @synopsis TAC_ARG_ENABLE_FEATURE_SUB(FEATURE_NAME, SUB_FEATURE_NAME, FEATURE_DESCRIPTION, HAVE_NAME, DEFAULT_VAL)
|
||
|
|
dnl
|
||
|
|
dnl This hack gets around the fact that TAC_ARG_ENABLE_FEATURE does not support underscores
|
||
|
|
dnl in its feature names. TAC_ARG_ENABLE_FEATURE_SUB allows exactly one underscore. Not great,
|
||
|
|
dnl but arguably better than supporting no underscores.
|
||
|
|
dnl
|
||
|
|
dnl TAC_ARG_ENABLE_FEATURE(feature-sub, [Configure and build feature-sub], FEATURE_SUB, yes)
|
||
|
|
dnl fails because tac_arg_enable_feature tests for ac_cv_use_feature-sub which gets
|
||
|
|
dnl rejected because the `-' is not allowed in variables. (AC_ARG_ENABLE sets ac_cv_use_feature_sub
|
||
|
|
dnl to avoid this problem.) Use:
|
||
|
|
dnl
|
||
|
|
dnl TAC_ARG_ENABLE_FEATURE(feature, sub, [Configure and build feature-sub], FEATURE_SUB, yes)
|
||
|
|
dnl instead.
|
||
|
|
dnl
|
||
|
|
dnl Test for --enable-${FEATURE_NAME} and set to DEFAULT_VAL value if feature not specified.
|
||
|
|
dnl Also calls AC_DEFINE to define HAVE_${HAVE_NAME} if value is not equal to "no"
|
||
|
|
dnl
|
||
|
|
dnl Use this macro to help defining whether or not optional
|
||
|
|
dnl features* should compiled. For example:
|
||
|
|
dnl
|
||
|
|
dnl TAC_ARG_ENABLE_FEATURE(epetra, [Configure and build epetra], EPETRA, yes)
|
||
|
|
dnl
|
||
|
|
dnl will test for --enable-epetra when configure is run. If it is defined
|
||
|
|
dnl and not set to "no" or not defined (default is "yes") then HAVE_EPETRA will
|
||
|
|
dnl be defined, if --enable-epetra is defined to be "no", HAVE_EPETRA will not
|
||
|
|
dnl be defined.
|
||
|
|
dnl
|
||
|
|
dnl *NOTE: epetra, aztecoo, komplex, ifpack, and other software found in
|
||
|
|
dnl subdirectories of Trilinos/packages are "packages" in their own right.
|
||
|
|
dnl However, these packages are also "features" of the larger package
|
||
|
|
dnl "Trilinos". Therefore, when configuring from the Trilinos directory,
|
||
|
|
dnl it is appropriate to refer to these software packages as "features".
|
||
|
|
dnl
|
||
|
|
dnl This file was based on tac_arg_enable_package.m4 by Jim Willenbring
|
||
|
|
dnl @author Ken Stanley <ksstanl@sandia.gov>
|
||
|
|
dnl
|
||
|
|
AC_DEFUN([TAC_ARG_ENABLE_FEATURE_SUB],
|
||
|
|
[
|
||
|
|
AC_ARG_ENABLE([$1-$2],
|
||
|
|
AC_HELP_STRING([--enable-$1-$2],[$3 (default is [$5])]),
|
||
|
|
ac_cv_use_$1_$2=$enableval, ac_cv_use_$1_$2=$5)
|
||
|
|
|
||
|
|
AC_MSG_CHECKING(whether to use [$1-$2])
|
||
|
|
|
||
|
|
if test "X$ac_cv_use_$1_$2" != "Xno"; then
|
||
|
|
AC_MSG_RESULT(yes)
|
||
|
|
AC_DEFINE([HAVE_$4],,[Define if want to build $1-$2])
|
||
|
|
else
|
||
|
|
AC_MSG_RESULT(no)
|
||
|
|
fi
|
||
|
|
])
|
||
|
|
|