Samuel Burbulla authored 4 years ago and Andreas Dedner committed 4 years ago

Update dependencies.

fix the order in which dune modules are processed when calling `make install_python` with `setup-dunepy`.
Also add a `pyproject.toml` to make sure `wheel` is available when installing dune-common. Also added `wheel`
to python dependencies in dune.module so that downstream modules can rely on `wheel` being available.

cmake arguments were stored as a dict, having mainly definitions in mind.

This lead to several issues, as cmake has many different kinds of
commmand line arguments.

Instead of storing these arguments as a dict, we now only store them as
a list, which can directly be passed to Popen, when spawning the cmake
process.

Fixes #238.

Samuel Burbulla authored 4 years ago and Andreas Dedner committed 4 years ago

don't need shared libs to install dune modules so adapted packagedata
accordingly - this solves the issue of having to prescibe some relative rpath

Also do not require setup.py/pyproject.toml to be added to git

Samuel Burbulla authored 4 years ago and Andreas Dedner committed 4 years ago

Add relative CMAKE_INSTALL_RPATH.

added CMAKE_BUILD_PATH to the rpath of python modules as well

added missing package include

add CMAKE_INSTALL_RPATH_USE_LINK_PATH to setup.py cmake flags to avoid
issue with missing rpath entries for CMAKE_PREFIX_PATH

Do not add suggestions any more.

Samuel Burbulla authored 4 years ago and Andreas Dedner committed 4 years ago

Reset LD_LIBARY_PATH when call deactivate.

Fix dynamic_lookup.

add option to `dunepackaging` script to only build sdist but not upload

exti with code 0 in dunepackaging.py -c so it can be used with dunecontrol

also set the `LD_LIBRARY_PATH`

[bugfix] used the wrong way to access the path to a sourced script - was working by chance

Samuel Burbulla authored 4 years ago and Andreas Dedner committed 4 years ago

make setup-dunepy.py work again without an installed dune-common

remove unused default cmake options for building dune-py

Add git checkout setup.py pyproject.toml to dunepackaging -c.

make it possible to use setup.py without having an installed dune-common python package. This requires having the PYTHONPATH set as it is now done in dune-common/bin/dunepackaging.py

[bugfix] previous commit

[bugfix] previous commit

set the correct 'prefix' in the pc files if SKBUILD is set, i.e.,
a wheel is being build using scikit-build

to automate generation of metadata for setup.py for other modules

[bug fix] previous commit

move files around a bit to be able to use the metaData extraction
from dunepackaging.py

use more of the cmake variables in python/setup.py.in

fix an issue in dunepackaging.py for modules without a python package

- remove CMakeCache.txt file in dune-py
- check that pyproject.toml file contains all dune module dependencies
  mentioned in dune.module to check consistency

[bug fix] previous commit

add dune modules from pyproject.toml to install_requires in setup.py

[bug fix] previous commit

added files generated when calling python setup.py sdist to git ignore list

Update bin/dunepackaging.py.

Add path to dunepackaging if dune-common.

Append version number devDATE to -git versions and add suggestions if they have a pypi package.

Samuel Burbulla authored 4 years ago and Andreas Dedner committed 4 years ago

Remove __pycache__.

Add CMAKE_MACOSX_RPATH=TRUE.

experiment with extracting required meta data for generating setup.py from
- dune.module file
- pkg_resource
This version does not require an extra project.py file but does assume that
the python module for which setup.py is to be generated is installed. Also dune.common
must be available:
- dune.common.module.Description class is used to parse dune.module file
- pkg_resource is used to extract additional metadata information (as provided by
  python/setup.py.in) requiring the module to be installed. This data is
  'description' ('Summary'), 'url' ('home-page'), 'author', and the install_requires.
  At the moment this will fail e.g. for dune-localfunctions which has no python
  package. We could decide to add the required information to dune.module and use
  replacements in python/setup.py.in instead.

Parse meta data from dune.module and setup.py.in.

add a try except around trying to open python/setup.py.in

Carsten Gräser authored 4 years ago and Andreas Dedner committed 4 years ago

This adds an optional parameter `--module=mod` to `setup-dunepy.py`.
If this parameter is passed, only `mod` and its dependencies are
used as dependencies of the newly created dune-py module. This allows
to do
```
dunecontrol --opts=my.opts --module=foo all
setup-dunepy.py --opts=my.opts --module=foo install
```
which would otherwise fail if `setup-dunepy.py` tries to process
found modules that have not been build by `dunecontrol`. If the
option is not passed all found modules are used as dependencies
as before.

add numpy, mpi4py to required packages

remove some python 2 related code and fixed up some other issues
pointed out by Timo
deprecated old compatibility file - move Python 3 code to dune.common.utility

FieldVector/Matrix classes with low dimension

add all flags to pybind11 modules

move bin files and cmake modules from dune-python
add sphinx support from dune-python

Make the comments a tiny bit more meaningful.

Add the 'Suggests' field, to make it more obvious that optional
dependencies are possible.

Ansgar Burchardt authored 5 years ago and Christoph Grüninger committed 5 years ago

The name git-whitespace-hook is a bit too generic for a DUNE-specific
tool.

Autotools is gone quite some time now. No need to keep this tools.

Apparently, this option has been around since 2009, but somehow
it never made it into the man page and the output of -h.

'configure' is an old alias for 'cmake', back from the
good old AutoTools days.

As it turns out, older versions of CTest do not output a "Completion Status" for
tests that were not run, so we need a fallback. The only place for information
is the test output, which we parse for certain key phrases to detect tests that
were skipped or had missing requirements (typically due to compilation
failures).

The build directory does not really work here, because it will just be called
build-cmake. So extract it from the CI_PROJECT_NAME variable and normalize that.