#783 add file with summary information of modules found in configure
Metadata
Property | Value |
---|---|
Reported by | Andreas Dedner (A.S.Dedner@warwick.ac.uk) |
Reported at | Apr 28, 2010 11:59 |
Type | Feature Request |
Version | Git (pre2.4) [autotools] |
Operating System | Unspecified / All |
Last edited by | Martin Nolte (nolte@mathematik.uni-freiburg.de) |
Last edited at | Jun 4, 2010 09:53 |
Closed by | Martin Nolte (nolte@mathematik.uni-freiburg.de) |
Closed at | Jun 4, 2010 09:53 |
Closed in version | Unknown |
Resolution | Implemented |
Comment | The patches are applied in revision 6031 (dune-common) and 6740 (dune-grid) |
Description
Sometimes it is difficult to figure out which modules/libraries were found during configure - especially the versions and paths. The summary information at the end of the build process is not in config.log and there is so much output (on screen or in config.log) that is would be hard to find in any case. Also the fact that something was found (yes) is often not sufficient information (version/path would be better).
Attached is a patch for dune-common and a patch for dune-grid showing how to use the changed m4 macros in the case of alu and alberta.
In dune-common we changed the macro DUNE_ADD_SUMMARY_ENTRY: the macro now writes information to the screen as before and additionally to a file dune.summary. To allow more detailed information in the summary file a second optional argument can be supplied.
Exanple: DUNE_ADD_SUMMARY_ENTRY([ALUGrid],"version 1.2","path") leads to ALUGrid.................: version 1.2 on screen and to ALUGrid.................: version 1.2 (path) in the dune.summary file.