| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0003002 | CMake | CTest | public | 2006-03-27 00:33 | 2010-12-14 18:45 | ||||
| Reporter | Sebastien Barre | ||||||||
| Assigned To | David Cole | ||||||||
| Priority | normal | Severity | feature | Reproducibility | always | ||||
| Status | closed | Resolution | won't fix | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0003002: REQ: CTest: CTEST_INSTALL | ||||||||
| Description | Would be great if there was a CTEST_INSTALL command on top of the usual ones (CTEST_CONFIGURE, CTEST_BUILD, CTEST_TEST). Doing so with EXEC_PROGRAM is non-trivial, especially if you want to support the /I flag so that installation does not fail completely if something was missing (say, I build and install the examples; even if an example did not build correctly (say, because of an external lib), it would be nice if at least my libs install correctly). | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0013856) David Cole (manager) 2008-10-10 18:05 |
Resolving as "Won't Fix" because: You can basically achieve this with the ctest of CMake 2.6 by setting CTEST_BUILD_TARGET to "install" before calling CTEST_BUILD to build the "make install" target. (Works with makefile generators and with Visual Studio or Xcode. Probably the other generators, too...) Or you could set it to "package" to build the "make package" target. If the build fails in any way, it will not install... but that is as it should be. Also because: how should ctest install the project: should it do a make install or a make package and then run the produced installer? If running an installer, should it be "forced silent / no dialogs" so that it can be run from a script? It will have to handle installing things with/without admin privileges, with/without absolute install paths, and probably other nightmares I'm not even thinking of. There are probably so many project specific aspects of this "ctest feature" that it actually makes more sense to leave it in the hands of the project script developers out there. (Tag! You're it!) If you disagree with this resolution, feel free to re-open the issue and attach your arguments in a new Note. Thx, David |
|
(0024029) David Cole (manager) 2010-12-14 18:45 |
Closing bugs that have been resolved for more than 3 months without any further updates. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2007-08-31 11:28 | Alex Neundorf | Assigned To | System Admin => David Cole |
| 2008-10-10 18:05 | David Cole | Status | assigned => resolved |
| 2008-10-10 18:05 | David Cole | Resolution | open => won't fix |
| 2008-10-10 18:05 | David Cole | Note Added: 0013856 | |
| 2010-12-14 18:45 | David Cole | Note Added: 0024029 | |
| 2010-12-14 18:45 | David Cole | Status | resolved => closed |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |