Hi Julio, On Wednesday 24 July 2013 11:41:04 Júlio Hoffimann wrote: > It's my first time trying to build OPM. As far as I understood, I need to > clone all repositories in the same directory and, assuming all dependencies > are installed, run the dunecontrol tool at the root: > > $ ./dune-common-2.2.1/bin/dunecontrol all
so far, this should be okay.
> Again, if I understood it correctly, this is just a script that will check
> for all dune modules in the current directory and run the configure/make
> accordingly.
yes. another option is to enter the directory of the the opm module you which
want to build, and run 'cmake .' within it. In this case, you have to manually
compile all prerequisites upfront (i.e. all required DUNE/OPM modules).
> I'm having a hard time trying to fix some linkage errors, could you please
> guide me to the most up-to-date build steps? Is the CMake build fully
> working?
you will always use cmake since the last release; the 'configure' script now is
just a shallow compatibility layer to make dunecontrol happy.
could you be a bit more specific about which linker errors you see, and for
which module? One possibility is that, in addition to the dune tarballs which
manually unpacked, you installed some DUNE packages provided by your linux
distribution. This might lead to missing symbols if opm does not link in
libraries which were used by the distribution package.
cheers
Andreas
--
If the programmers like each other, they play a game called "pair
programming". And if not, then the game is called "peer review".
-- Anna Nachesa
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
