Maintaining new Dune modules and applications

dune.module

dune.module keeps all dependency information for a certain Dune module. Possible entries are:

Module: ...

Name of the module this name must consist only of alphanumerical characters.

Depends: ...

Space separated list of modules this module needs. With out these dependencies it is not usable

Suggests: ...

Space separated list of modules this module does not depend on, but can use. These modules make further features of this module available.

Example (dune-istl):
Module: dune_istl
Depends: dune_common

configure.ac

The configure.ac of an application contains an entry DUNE_CHECK_ALL. This command now takes a comma separated list of modules it wants to check. When writing a module you should use the variant DUNE_CHECK_ALL_M.

Example (dune-istl):
...
DUNE_CHECK_ALL_M([dunecommon])

if test x$HAVE_DUNECOMMON != x1 ; then
  AC_MSG_ERROR([Can't work without the dune-common module. Maybe you have to supply your dune-common directory as --with-dunecommon=dir])
fi

AC_SUBST([AM_CPPFLAGS], ' -I')
AC_SUBST([AM_LDFLAGS], ' ')

DUNE_SUMMARY_ALL
...