[dunecontrol] Module without CMakeLists.txt next to dune.module is installed

The decision whether a module is installed is usually based on whether pkgconfig was able to find it. If the DUNE module does not ship a pkgconf file or pkgconf is missing, then dunecontrol tries to build this installed modules, too. That fails miserably.

With this commit we add a check at the end that checks whether there is a CMakeLists.txt file in the source directory of the module. This directory is where the dune.module file was found. If there is none we also assume that the module is installed and do not try to build it.

Closes #399 (closed)

The whole part about pkg-config files should eventually be removed. The pkg-config files currently still provided in the dune modules will either be removed completely, or be fixed. Then the decision whether a dune modules is an installed module or not should not be based on the existence of these files.

For now, the MR is a quickfix. I cannot really judge whether this MR is correct or not. The system test uses installed modules. If this passes, I would click on merge.

added 42 commits

• afbd393c...5b2977aa - 41 commits from branch master
• c005e09b - [dunecontrol] Module without CMakeLists.txt next to dune.module is installed

Compare with previous version

resolved all threads

merged

mentioned in commit f8a36d59