I use a similar setup as Bård, and I am also reluctant to abandon the so-called 
sibling builds.

Having heard that various meta-project will solve the same, I am willing to try 
them out, what
should I be using instead?

My main concerns are that:
 - it must not be too hard to make a "developer's install" (although it can be 
harder than a "user's install")
 - that install must contain only a single working directory for any module 
(that then can be used to build all configs desired)
 - our current install docs (while outdated in the face of opm-cmake) assume a 
sibling build

Also: what is the purpose of removing this? What are the user errors we are 
trying to prevent? How significant is the simplification
of the build system that will result? I know we discussed this at the OPM 
meeting a few months ago, but I'd like to know the
motivation behind this a little better.

Thanks for making a discussion out of this rather than just doing it…!

Atgeirr


_______________________________________________
Opm mailing list
[email protected]
http://www.opm-project.org/mailman/listinfo/opm

Reply via email to