Dear OPM community, Many of us feel that our current module/repository structure is a little confusing and should be improved. For example, from the name, one would expect that opm-core would be the single module on which all others depend, but that is not the case.
We should move forward one small step at a time, if possible, to minimize disruption to ongoing work. After some discussion on github and the wiki (http://www.opm-project.org/wiki/index.php/OPM_reorg_2015) I propose the following small change to start off: rename opm-cmake to opm-common. The intention is that opm-common will become the central module upon which all others depend. Already, since all modules use the build system from opm-cmake, it is needed by all others. It will grow (primarily by moving code there from other modules) so that it will contain C++ code in addition to the build system's CMake things that are already there. If this is acceptable, I would like to make this change next week, and announce when it is completed on the mailing list so that everyone gets a chance to update their work. Since the opm-cmake module was introduced after the last release it will not affect the released binary packages, and to those who only follow releases it will be as if it was always named opm-common. I have one more question: we currently use the OPM_CMAKE_ROOT variable to give the location of the opm build system. Should we change this to OPM_COMMON_ROOT? Going forward, we'll have more issues to discuss related to restructuring. For example: should we make opm-common a header-only library? Should we allow it to depend on third-party libs such as boost? Atgeirr
_______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
