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

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Oliver Sander (sander) 

Attached to Project - Dune
Summary - Explain in the build system tutorial how hand-written modules can be tested for
Task Type - Bug Report
Category - Documentation
Status - New
Assigned To - 
Operating System - Unspecified / All
Severity - Low
Priority - Normal
Reported Version - SVN (pre2.1)
Due in Version - Undecided
Due Date - Undecided
Details - 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).


More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=814

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.