[Dune] [#604] move reference element related stuff to separate module

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#604 - move reference element related stuff to separate module
User who did this - Jö Fahlke (joe)

----------
Suggesting dune-geometry in dune-common should yield interesting results.
AFAIK, if a suggested module is found dunecontrol will make sure it is build
before the module suggesting it.  So this would lead to a loop in dunecontrol.

The "warning if found, error if not found" behaviour can be achieved by my
first approach without any autohell-magic:

#warning This header is deprecated.  Use <dune/geometry/geometrytype.hh> from
#warning the new Dune module Dune-Geometry instead.
#warning
#warning If the following include statement gives you an error, you need to
#warning install the new Dune-Geometry module, and make sure that your module
#warning depends on it.
#include <dune/geometry/geometrytype.hh>

The only missing thing is the automatic fallback to a compatibility
implementation of GeometryType in Dune-Common.  To achieve this I see three
possibilities:

 1. Check for Dune-Geometry in Dune-Common's configure.  This is most probably
    unrealiable, if at all feasible.

 2. Try to shadow Dune-Common's <dune/common/geometrytype.hh> by providing a
    header with the same name and path in Dune-Geomtry as well.  Again, this
    is probably unreliable, and it requires that the -I flags are given in a
    certain order.

 3. Have a flag --enable-old-geometrytype in Dune-Common's configure, which
    people must set explicitly.  This may play havoc with out-of-source
    builds, and since the user has to take action anyway, he could just as
    well install Dune-Geometry and add it to his application module's
    dependency list.

For each of the possibilities I wonder whether they are worth the trouble.




----------

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

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.