Just for the record:
While OPM might compile with DUNE 2.6 in a Vanilla/Default configuration, it
seems broken if e.g.
- BUILD__TESTING is ON for opm-models because of
https://github.com/OPM/opm-models/blob/master/opm/models/nonlinear/newtonmethod.hh#L191
There is no equivalent method in DUNE 2.6
- or dune-alugrid/dune-fem are enabled.
Am Tue, Oct 04, 2022 at 06:31:28AM +0000 schrieb Atgeirr Rasmussen:
Hi,
Circling back to Arne Morten's point, that we would have to backport Dune and
put it in our own ppa to use the newer Dune releases, how much work would that
be? And if we did that, could/should we skip straight to Dune 2.8 or even 2.9?
If we set as a goal to:
- Use and require as new Dune as feasible (say 2.8 for now).
- Use and require as recent C++ standard as feasible (we now require C++17, but
say we want to use C++20).
Other than developers updating their systems (which I consider quite acceptable
as long as we do not require bleeding-edge versions), and the above-mentioned
backporting, what else would we need to do? I assume Jenkins and Debian may be
points of difficulty.
Atgeirr
_______________________________________________
Opm mailing list
[email protected]
https://opm-project.org/cgi-bin/mailman/listinfo/opm
--
Markus Blatt
CEO @ OPM-OP AS, Heyerdahlsvei 12b, 0777 Oslo, Norway
https://opm-op.com | +4916097590858
_______________________________________________
Opm mailing list
[email protected]
https://opm-project.org/cgi-bin/mailman/listinfo/opm
