Skip to content
Snippets Groups Projects
  1. Jul 12, 2023
  2. Jun 30, 2023
  3. Sep 30, 2022
  4. Oct 22, 2021
    • Andreas Dedner's avatar
      use new approach in dune-common for handling python bindings · 825d5560
      Andreas Dedner authored
      fix ci
      
      pep 42: use implicit namespace packages which make it possible to combine subpackages using editable (source) and non editable (pypi)
      
      only use a cmake install a python module in the SKBUILD setting - for an install from build dir pip will take take of this since it is part of the setup.py file
      
      add a stopgap solution unti ci repo up and running again
      
      Update requirements.
      
      add dune packages to requires in setup.py.in
      
      [testing]
      
      only add dune modules that have been found as requirements in setup.py.in
      
      removed setup.py.in since the default is provided in dune-common
      
      adapt ci yml file to python bindings on by default
      
      disable python bindings for clang 5 (ubuntu 18) since no numpy matching numpy version can be installed from the gitlab registry
      
      [bug fix python bindings]
      fix an issue with 'entry' being used in implicit build mode but ready==build
      825d5560
  5. Nov 18, 2020
  6. Nov 17, 2020
  7. May 25, 2020
  8. May 24, 2020
  9. Mar 30, 2020
  10. Mar 27, 2020
  11. Apr 25, 2018
  12. Jan 29, 2018
  13. Jan 09, 2018
  14. Jan 02, 2018
  15. Oct 20, 2017
  16. Jun 28, 2017
    • Martin Nolte's avatar
      [cmake] add macro dune_add_pybind11_module · 92a7bdbc
      Martin Nolte authored
      Building Python modules through Pybind11 is a recurring task in our
      Python bindings. To reduce maintainance in the build system, we introduce
      a CMake function "dune_add_pybind11_module", which is semantically inspired
      by the "dune_add_test" function.
      92a7bdbc
  17. Apr 28, 2017
  18. Aug 05, 2016
  19. May 28, 2016
  20. Jan 22, 2016
  21. Jan 02, 2014
  22. Jun 05, 2013
    • Markus Blatt's avatar
      [CMake] Guess build directory of dune-common · da5f82f4
      Markus Blatt authored
      Previously we relied on CMake's export(PACKAGE ...) function when
      finding dune packages without dune-control. This is error prone
      when using several instances of a dune-module (either with differing
      versions or built using different options). In this case there is no
      control which of the instances is used.
      
      Now we try to guess the correct build directory, if it was not
      provided with ${module}_DIR, ${module}_Root or in the
      CMAKE_PREFIX_PATH. Note that when using dunecontrol ${module}_DIR will
      always be set. We take the path of the current toplevel build
      directory and simply substitute any occurence of the name of current
      module with name of the module that we try to find. This works for
      both  building in a subdirectory of the source tree
      (e.g. ${module-source}/build-cmake) or in a sibling directory
      da5f82f4
  23. Feb 20, 2013
  24. Oct 19, 2012
  25. Sep 27, 2012
    • Markus Blatt's avatar
      - List the cmake modules explicitly (file(GLOB will not detect changes · b1b6e414
      Markus Blatt authored
        after configure)
      - Make CMake module installation path configurable
      - Detect CMAKE_MODULE_PATH automatically
        + First call find_package(dune-common) to query its CMAKE_MODULE_PATH
        + Then setup the module path
        + After each find_package of dune module update the CMAK_MODULE_PATH
        + each module exports ist own <package-name>_MODULE_PATH in the
        + package configuration files
      
      [[Imported from SVN: r1714]]
      b1b6e414
  26. Sep 20, 2012
  27. Aug 28, 2012
  28. May 22, 2012
  29. Apr 30, 2012
Loading