#1532 cmake forgets flags if dunecontrol is called twice
Metadata
Property | Value |
---|---|
Reported by | Carsten Gräser (graeser@math.fu-berlin.de) |
Reported at | Nov 24, 2014 13:11 |
Type | Bug Report |
Version | Git (pre2.4) [autotools] |
Operating System | Unspecified / All |
Last edited by | Dominic Kempf (dominic.r.kempf@gmail.com) |
Last edited at | Feb 3, 2015 10:03 |
Closed by | Dominic Kempf (dominic.r.kempf@gmail.com) |
Closed at | Feb 3, 2015 10:03 |
Closed in version | 2.4 |
Resolution | None |
Comment | Implemented issuing a warning: |
bca30529d40895aef32fbf213e175b57737ac62a |
The general problem is fixed upstream. |
Description
With a newly checked out dune-common I observe the following. After running
./dune-common/bin/dunecontrol --opts=dune.opts all
with the attached options file, cmake if correctly configured with the supplied compiler options. E.g. calling
grep funroll dune-common/build-cmake/CMakeCache.txt
reveals the -funroll-loops option. If the same dunecontrol call is executed a second time cmake seems to miss all options passed by cmake_flags, e.g., the funroll-loops flag. The same is true for prefix paths.