[Dune] first release candidate for 2.6 release

[Markus Blatt]

Hi,

Happy new guys.

Seems like this year continues like the last with more demanding DUNE
prerequisites.

On Tue, Jan 02, 2018 at 01:22:50AM +0100, Christoph Grüninger wrote:
> thanks for sharing the progress with Dune 2.6. I gave it a try with
> Clang 5 and CMake 3.10.
> 
> * I successfully compiled the core modules and their tests.
> * I successfully compiled some more modules and their tests: alugrid,
> uggrid, typetree, functions
> * I tested DuMuX 3.0 alpha and the failures are related to DuMuX.
> 
> Overall, I am positive. What should be addressed:
> 
> * dune-grid's mcmgmapper test could work around the deprecation warnings
> * dune-functions requires CMake 2.8.12. Dune common 2.6 will require
> CMake 3.1.


Why DUNE demands Cmake 3.1 is beyond me. I did test dune-istl and
dune-grid with 3.0 and it worked. 

> Thus, when CMake is executed for dune-funtions, all policies
> are set for 2.8.12. This leads to a warning and might lead to sublte
> bugs.

Last time I checked CMake did have compatibility modes and these would
be activated if a specific version was requested. I have never
experienced subtle bugs. Would you mind to point out some of them that
you and/or others have experienced?

> I propose to bumb the required CMake version to 3.1 as well.
> Similar for dune-uggrid, dune-alugrid, DuMux, and probably for several
> modules more. I proposed such a change for dune-uggrid as !90, but it
> has been disputed.

IMHO this is a wrong direction especially for the release. In an ideal
world a build system should just work. Well DUNE is not a member of an
ideal world and we are already imposing more build system work
onto the user than we should (Read: The config.h and
DuneModuleMacros.cmake magic). Additionally demanding a higher CMake
version than needed is definitely a tad too much.

My route would be to demand an as low version of CMake as possible for
the core modules.

I am willing to do the work and test. Even though I am still quite
upset about what compatibility issues the cat dragged in just for the
sake of python support.

Cheers,

Markus

> * Unfortunately this is also true for some core modules like dune-grid.
> This should be fixed.
> 
> Bye
> Christoph
> 
> Am 22.12.2017 um 19:09 schrieb Andreas Dedner:
> > Hi everyone.
> > 
> > We just wanted to let you know that just in time for Christmas the first
> > release candidate of the 2.6 release is available for testing.
> > Tar balls are available
> > https://www.dune-project.org/releases/2.6.0rc1/
> > or use the v2.6.0rc1 tag for helping us, by testing the release with
> > your own modules, system, workflow... Let us know if you encounter any
> > problems. Also please skim through the change log (same link as above)
> > to see if something is unclear or missing.
> > 
> > Wish you all a merry Christmas and a happy new year
> > Andreas and Martin
> 




> _______________________________________________
> Dune mailing list
> Dune at lists.dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune


-- 
Using PT-Scotch with DUNE https://t.co/hZH8lxf5ZF

Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de
Pedettistr. 38, 85072 Eichstätt, Germany
Tel.: +49 (0) 160 97590858
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://lists.dune-project.org/pipermail/dune/attachments/20180103/7f1c8bef/attachment.sig>