#814 Explain in the build system tutorial how hand-written modules can be tested for

Metadata

Property	Value
Reported by	Oliver Sander (oliver.sander@tu-dresden.de)
Reported at	Jul 16, 2010 09:48
Type	Bug Report
Version	Git (pre2.4) [autotools]
Operating System	Unspecified / All
Last edited by	Christian Engwer (christi@conan.iwr.uni-heidelberg.de)
Last edited at	Oct 21, 2011 20:40
Closed by	Christian Engwer (christi@conan.iwr.uni-heidelberg.de)
Closed at	Oct 21, 2011 20:40
Closed in version	Unknown
Resolution	Fixed
Comment	Documentation was improved in the buildsystem-howto

Description

As Christian explained nicely on the list

You will have to add something like the following to project:

dumux/m4/dumux.m4:

dnl -- autoconf --

Macros needed to find dumux and dependent libraries. They are called by

the macros in ${top_src_dir}/dependencies.m4, which is generated by

"dunecontrol autogen"

Additional checks needed to build dumux

This macro should be invoked by every module which depends on dumux, as

well as by dumux itself

AC_DEFUN([DUMUX_CHECKS])

Additional checks needed to find dumux

This macro should be invoked by every module which depends on dumux, but

not by dumux itself

AC_DEFUN([DUMUX_CHECK_MODULE], [ DUNE_CHECK_MODULES([dumux],[dumux/dumux.hh]) ])

The macro DUMUX_CHECK_MODULE is required to find your module. If you didn't do any fancy tricks, the default version should do the trick. If you provide libraries, you should add the name of the lib to the DUNE_CHECK_MODULES entry (have a look at dune-grid for example).