#230 configure should support 'private' modules
Metadata
| Property | Value |
|---|---|
| Reported by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Reported at | Jan 4, 2007 19:53 |
| Type | Feature Request |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Apr 8, 2010 20:30 |
| Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Closed at | Apr 8, 2010 20:30 |
| Closed in version | Unknown |
| Resolution | Implemented |
| Comment |
Description
In order to test for a module during configure, this module must be mentioned in dune-common/m4/dune.m4.
This will not hold for long. When the fist 'private' modules occure this must be changed.
Necessary steps:
- generate full dependencies during autoconf
- read direct dependencies and from dune.module file
- allow per module m4-files
- update autogen.sh
- update duneproject