View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0013686 | CMake | CMake | public | 2012-11-15 15:07 | 2015-07-08 08:57 | ||||
Reporter | Dave Abrahams | ||||||||
Assigned To | Stephen Kelly | ||||||||
Priority | normal | Severity | feature | Reproducibility | always | ||||
Status | closed | Resolution | no change required | ||||||
Platform | Mac | OS | OS X | OS Version | 10.8.2 | ||||
Product Version | CMake 2.8.9 | ||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0013686: log the cmake command somewhere | ||||||||
Description | It's very common that I come back to a project after weeks and need to run the CMake command I originally used again, only slightly modified. There's no obvious place where I can find a record of that command. It would be great if that were stored someplace obvious and accessible for me. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0038091) Stephen Kelly (developer) 2015-02-26 16:16 |
There is no need to run the exact command again. CMake has already cached it. Running 'cmake .' in the build dir is equivalent and slight modifications like 'cmake . -DSOME_OPTION=OFF' work fine. |
(0039080) Robert Maynard (manager) 2015-07-08 08:57 |
Closing resolved issues that have not been updated in more than 4 months. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2012-11-15 15:07 | Dave Abrahams | New Issue | |
2015-02-26 16:16 | Stephen Kelly | Note Added: 0038091 | |
2015-02-26 16:16 | Stephen Kelly | Status | new => resolved |
2015-02-26 16:16 | Stephen Kelly | Resolution | open => no change required |
2015-02-26 16:16 | Stephen Kelly | Assigned To | => Stephen Kelly |
2015-07-08 08:57 | Robert Maynard | Note Added: 0039080 | |
2015-07-08 08:57 | Robert Maynard | Status | resolved => closed |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |