Hi Paolo, On Friday, June 20, 2014 18:36:22 Paolo Orsini wrote: > I built/installed : > - required packages (boost-devel, etc..) > - compile and install ERT (compiling and installing from source, from > current github master) > - compile and install opm-parser (did make test ... all good) > - compile and install opm-core (did make test ... all good) > > I tried to build the well example independently.
ah, that might explain it: you probably did not link your binary to libopmcore
and to the libraries produced by opm-parser. If you did, could you please
provide the full linker command which 'make' tries to execute?
Note that, instead of starting a project from scratch, it is probably easier
to just clone the OPM module which is closest to what you would like to
achieve and extend it by your stuff. The build system is pretty intricate and
with git it is easy to do local commits and occasionally rebase them on top of
the latest upstream version.
(finally, if you have developed stuff which might be interesting to others,
please open a pull request on github. this makes your life much easier as you
won't have to maintain the code after it has been accepted upstream and the
others do not need to re-implement your changes. We don't bite on reviews,
promised...)
> I am happy to follow the most common path to build/install ... which is?
it is that everybody should be able to do it as it pleases him most.
Personally I usually use the dunecontrol script (from the dune project)
because it takes care about prerequisite modules and compiles everything in
the right order, but most other developers use cmake directly in conjunction
with out-of-tree build directories (which are not really possible with
dunecontrol).
cheers
Andreas
--
Notice: "String" and "Thread" are the same thing to non-computing
people.
— Programming.com
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
