Ignores any modules that don't contain a module.cfg file. These can be left over when changing git branches where a module exists to one where it does not. Before this change, the presence of the directory alone would trigger CMake to run the module build scripts, which fail due to the lack of any module files. Without a module.cfg file, there is no module to build, so ignoring these sub-directories is the right thing to do, whether they are left over from changing branches or for whatever other reason.
Test Description
Hand tested before creating this PR. I don't see a good way to integrate a test for this.
Pull Request Title
Fixes #608
Change Description
Ignores any modules that don't contain a
module.cfg
file. These can be left over when changinggit
branches where a module exists to one where it does not. Before this change, the presence of the directory alone would triggerCMake
to run the module build scripts, which fail due to the lack of any module files. Without amodule.cfg
file, there is no module to build, so ignoring these sub-directories is the right thing to do, whether they are left over from changing branches or for whatever other reason.Test Description
Hand tested before creating this PR. I don't see a good way to integrate a test for this.