I'm on a MacOS Sierra (version 10.12.6).
----- Original message -----
From: Alf Birger Rustad <[email protected]>
To: Andres Codas Duarte <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: SV: [Opm] Help with installation
Date: Wed, Aug 2, 2017 12:42 PM
Hi Andres,
Dune 2.4.1 was used with rc1, but 2.3.1 should also work fine. Any other version may be problematic. I am on vacation, so a bit limited abilities to help you. Still, what distribution are you building on?
Cheers,
AlfFra: Opm <[email protected]> på vegne av Andres Codas Duarte <[email protected]>
Sendt: 2. august 2017 16:32:24
Kopi: [email protected]
Emne: Re: [Opm] Help with installationHi Atgeirr,Thank you!.What version of Dune should I use together with "testing/2017.06/rc1"? I checkout on version 2.4 and I got the following error when building opm-core:"In file included from /Users/codas/opm/opm-core/build/CMakeFiles/CMakeTmp/src.cxx:1:
In file included from /Users/codas/opm/opm-grid/dune/grid/CpGrid.hpp:62:
In file included from /Users/codas/opm/opm-grid/dune/grid/cpgrid/Intersection.hpp:52:
/Users/codas/opm/opm-grid/dune/grid/cpgrid/Geometry.hpp:48:10: fatal error: 'dune/geometry/genericgeometry/geometrytraits.hh' file not found
#include <dune/geometry/genericgeometry/geometrytraits.hh>"The full CMakeError.log is attachedI realized that there could be a misunderstanding in the version because the files for pkgconfig "dune-*.pc" say the version is "Version: 2.5.2-git" while I made sure to checkout on "releases/2.4" when installing.I'm confused, how do you recommend to proceed?. I just want to install on a recent version from sources so I can debug the code.ThanksAndres----- Original message -----
From: Atgeirr Rasmussen <[email protected]>
Sent by: "Opm" <[email protected]>
To: OPM Mailing List <[email protected]>
Cc:
Subject: Re: [Opm] Help with installation
Date: Wed, Aug 2, 2017 4:23 AM
Hello Andres!I checked-out on 63b7cf6febf3f41e59b8803c06994e12a550c46a (which is earlier than the one above), and continued with a successful installation.Good to hear!I realized that you are pushing new commits every few hours to the master branch of all the opm-modules. I guess these are not all properly unit-tested? How should I proceed to compile a 'stable' executable?Currently we only make stable releases every six months, as you know. In general, new commits are not accepted without testing. We use Jenkins at https://ci.opm-project.org to verify every pull request before it is merged, and as a rule patches are also reviewed before they are accepted. Inevitably, things go wrong once in a while, but the master branches are in a good state *almost* all the time.Recently, some extra testing was performed on a particular version (more recent than the April release), and the repositories were tagged to make it easy to reproduce that version. If you check out the tag "testing/2017.06/rc1" across all repositories you should get that version, which is quite well tested.If you want to stay current with ongoing development there is no way around using the master branches however.Atgeirr_______________________________________________
Opm mailing list
[email protected]
http://opm-project.org/cgi-bin/mailman/listinfo/opm
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorized use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you
_______________________________________________ Opm mailing list [email protected] http://opm-project.org/cgi-bin/mailman/listinfo/opm
