Hello; the dust has settled after the release and it is time to start breaking things again - what could be a better place to start than the build system? We have now prepared the following:
https://github.com/OPM/opm-cmake : This module contains a verbatim copy of the opm-core/CMake directory. Pull requests for all the modules: opm-parser: https://github.com/OPM/opm-parser/pull/439 opm-core: https://github.com/OPM/opm-core/pull/770 dune-cornerpoint: https://github.com/OPM/dune-cornerpoint/pull/132 opm-autodiff: https://github.com/OPM/opm-autodiff/pull/336 opm-polymer: https://github.com/OPM/opm-polymer/pull/95 opm-material: https://github.com/OPM/opm-material/pull/22 opm-upscaling: https://github.com/OPM/opm-upscaling/pull/143 ewoms: https://github.com/OPM/ewoms/pull/15 porsol: https://github.com/OPM/opm-porsol/pull/118 opm-benchmarks: https://github.com/OPM/opm-benchmarks/pull/53 opm-verteq: https://github.com/OPM/opm-verteq/pull/73 [I stumbled a bit in my rebase++ efforts here] The structure for all of the PR's is identical: 1. Change the logic for locating opm cmake modules: https://github.com/joakim-hove/opm-core/commit/9cb13141ba0fc03be0bb7b9ab5939b3c94bdf616 2. Remove the complete cmake/ directory. The medium term goal is obviously to make the freaking best cmake based build system the world has ever seen; in particular it should be robust, simple to use and extend and so on - basically a joy to work with! The short term goal is considerably less ambitious: We want to make a build system which is functionally 100% identical to the existing - warts and all, with the only difference that all the cmake modules are assembled in one shared repository. When we have assembled all the modules in one repository we are in much better shape for further improvements of the build system. If we do not receive clear objections we will merge this on the 14.th of Mai. Further plans which we can work with after this has been merged: 1. A meta-build system which is capable of build and download of module dependencies. 2. Better organization of the internal dependencies; currently all the dependencies will be maintained in opm-cmake, the dependencies (i.e. the opm-xxx-prereqs files) should be maintained in the appropriate repository. 3. Kill the sibling builds. 4. ???? Joakim Joakim RDI project with IT elements -> Contact R&D Toolbox<https://statoil.service-now.com/selfservice/catalog_item_detail.do?sysparm_document_key=sc_cat_item,78bfbbce6fb455001f6446916e3ee453> ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised 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://www.opm-project.org/mailman/listinfo/opm
