[Dune] dependance on user modules

[Christian Engwer]

Hi Carsten,

You can not create a new module using duneproject. Please read the
buildssystem howto
http://dune-project.org/doc/buildsystem/buildsystem.pdf
There is also a brief description on the differences between modules
which provide functionality to oder modules and pure applications.

There will be smaller changes you have to do to the buildsystem of
your module. But still there will be further difficulties...  The main
problem is, that currently all _real_ modules have to listed in the
dune.m4 in the DUNE_CHECK_DISPATCH function.

There are plans to improve the m4 situation, but we didn't see much
need to do this before the first release, as it would require big
changes to the buildsystem.

If the information in the howto is not sufficient feel free to ask
further questions :-) ... This week I can still answer them ...

Christian

On Wed, Aug 16, 2006 at 03:29:01PM +0200, Carsten Graeser wrote:
> Hi,
> I'm trying to put some common stuff for several applications in a separated
> dune module. I did the following:
> 
> 1) Generate a module 'cg-common' by duneproject requiering the four 
> 'dune-...' modules
> 2) Run 'dunecontrol --opts=my.opts all'
> 
> 3) Generate a second module 'mmg' by duneproject requiering the four 
> 'dune-...' modules
>    AND 'cg-common'. (This is offered by duneproject)
> 4) Running 'dunecontrol --opts=my.opts all' once again I get
> 
> [..]
> checking for dune-istl
> checking dune/istl/allocator.hh usability... yes
> checking dune/istl/allocator.hh presence... yes
> checking for dune/istl/allocator.hh... yes
> configure: dune-istl does not provide libs
> configure: error: Unknown module cg-common
> --- Failed to build mmg ---
> 
> I also tried to use DUNE_CHECK_ALL_M in cg-common/configure.ac
> (though I'm not sure what really means) and get the same result.
> 
> What am I doing wrong ?
> 
> Carsten
>