[Dune] Supporting both DUNE 2.4 and current master in external modules

[Ansgar Burchardt]

Hi,

I'm trying to support at least DUNE 2.4 (or even 2.3 as well) and the
current master in some external modules, at least as long as this is
possible without too much pain.  I'm a bit curious if other people also
try to support multiple DUNE versions in external modules; it might be
nice to have a list to handling common issues (like the EntityPointer
changes in 2.4 or build system changes in master mentioned below).

So far only the changes how CMake builds the tests seem to have changed
in incompatible ways.  As a workaround I added

  set(DUNE_REENABLE_ADD_TEST 1)

to CMakeLists.txt to get back add_test.

In addition I disabled the old magic by

  set(DUNE_TEST_MAGIC 0)

and removed the calls

  add_directory_test_target(_test_target)
  add_dependencies(${_test_target} ${TESTS})

This means the tests are now built during "make all", but it looks like
it should work with both DUNE 2.4 and current master (and even 2.3).

I know this doesn't follow the best practices for either release, but I
would like to avoid version dependent special cases.

Ansgar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <https://lists.dune-project.org/pipermail/dune/attachments/20151201/259d4971/attachment.sig>