Make c/c++ interface private

[sondreso]

We will make the c/c++ interface of resdata (formerly known as ecl/libecl) private.

The rationale is that there are a lot of functionality that is only exposed in c/c++ which is in little use, and we would like to clean this up in order to have a library that is easier to maintain. ert used to be a big consumer of this interface, but this is not the case anymore.

The next step is ta create a new major version bump of Resdata with the c/c++ interface as private. This means all comments in README and documentation about the c/c++ interface will disappear. Also the following lines will be removed:

resdata/python/resdata/__init__.py

Line 69 in c62737a

return ctypes.CDLL(path, ctypes.RTLD_GLOBAL)

resdata/setup.py

Line 86 in c62737a

"-DCMAKE_INSTALL_INCLUDEDIR=python/resdata/.include",

Note: The binaries exposed by resdata is still considered public:

resdata/setup.py

Lines 37 to 53 in c62737a

	"CF_dump",
	"convert.x",
	"rd_pack.x",
	"rd_unpack.x",
	"grdecl_grid",
	"grdecl_test.x",
	"grid_dump.x",
	"grid_dump_ascii.x",
	"grid_info.x",
	"kw_extract",
	"kw_list.x",
	"load_test.x",
	"make_grid",
	"ri_well_test",
	"segment_info",
	"select_test.x",
	"summary.x",

[magnesj]

Hi, due to historical reasons, we have a copy of the resdata repository in ResInsight using the C++ interface only, not the Python interface. We are asked to evaluate using the official resdata repository instead of a local copy. For ResInsight it is required to be able to access and use the C++ code in resdata using CMake. Please make sure that using C++ still will be possible.

Here is our copy (4-5 years since last sync with the public repository)
https://github.com/OPM/ResInsight/tree/dev/ThirdParty/Ert

[eivindjahren]

Here is our copy (4-5 years since last sync with the public repository)
https://github.com/OPM/ResInsight/tree/dev/ThirdParty/Ert

@magnesj seeing as your copy and resdata has diverged quite a bit, would it not be simpler to keep these projects separate? You can still apply patches from resdata without using the cmake file, but given how much divergence there is, that might very rarely be possible.

Also, the goal of resdata is to maintain the backwards compatability of the python interface, where historical artifacts like util_abort become difficult to deal with. Freed from the need to maintain the python interface, resinsight could deal with that in a standard c++ way: smart pointers, RAII, and exceptions.