#1525 Build directory per module or one containing the dirs for all modules?
Metadata
Property | Value |
---|---|
Reported by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
Reported at | Nov 7, 2014 06:47 |
Type | Discussion |
Version | 2.3 |
Operating System | Unspecified / All |
Last edited by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
Last edited at | Nov 17, 2014 16:46 |
Closed by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
Closed at | Nov 17, 2014 16:46 |
Closed in version | 2.4 |
Resolution | Not a bug |
Comment | There is not enough interest in such a change and a workaround. Maybe we want to change that in the future, if more people use out-of-source builds. |
Description
CMake will introduce out-of-source builds for everyone by default. It is even required for building the LaTeX documentation. Before switching to CMake as the default build system (#1500 (closed)), I want to discuss this issue to not make another disruptive change shortly after the CMake switch.
Currently, we create a directory, build-cmake if not specified differently by the user, directly below every module. So every module contains one or even more build directories. This behavior is still from the autotools days and I adopted the way.
As Dominic pointed out in #1510 (closed), it seems more natural to him, to have a build directory and for every module a sub-directory is created in the build directory. This is supported by dunecontrol, too. The user has to specify an absolute path as the build-dir.
What do you think, is the more natural approach? I tend to say that Dominic's point of view is right. Are there technical reasons to prefer one?