Feature/add python bindings
As discussed at the developer meeting (in 2018) the Python bindings are being moved from dune-python into the core modules.
Corresponding merge requests are open in dune-geometry, dune-grid, dune-istl, dune-alugrid, dune-spgrid, dune-polygongrid and in dune-fem,dune-fem-dg,dune-vem
I want to merge this quickly because rebasing all the merge request will get more involved the longer I wait. @all so if there are any comments please let me know
Merge request reports
Activity
added 1 commit
- b45e2292 - reduce compile time during the build of dune-common by not preregistring
assigned to @andreas.dedner
mentioned in issue #189 (closed)
added 1 commit
- 284a3913 - imporve handling of includes in `importclass.py`
- Resolved by Carsten Gräser
Can we get a minimal documentation of how to setup, build, and use the python bindings?
- Last reply by Andreas Dedner
Resolved by Andreas DednerI would say if one wants to be safe, then what is described above (Andreas's way of doing it) should be the way to go.
However, there is other ways to setup the whole tool chain, for example without shared libraries and without setup-dunepy.py.
Not using shared libraries one has to ensure -fPIC (and probably -fPIE) is enabled during compile. Not using shared libraries may nonetheless lead to some problems in some cases. For example, when using UGGrid, shared libraries must be used which is related to the use of static variables inside libraries (staging/dune-uggrid#46 (closed)).
Not using setup-dunepy.py requires the user to set the environment variable PYTHONPATH by hand to DUNE_MODULE/build-cmake/python for all found DUNE_MODULE. This is what I do and it works fine for me. It is not the pythonic way of doing things though.
- Last reply by Andreas Dedner
added 1 commit
- 0af09897 - [feature][DUNE_ENABLE_PYTHONBINDINGS] Added cmake option for enabling
