| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0014307 | CMake | CMake | public | 2013-07-24 05:22 | 2013-12-02 08:51 | ||||
| Reporter | ycollet | ||||||||
| Assigned To | |||||||||
| Priority | normal | Severity | feature | Reproducibility | always | ||||
| Status | closed | Resolution | won't fix | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | CMake 2.8.9 | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0014307: add a COMMENT option for execute_process | ||||||||
| Description | A COMMENT option for execute_process should be nice. To do things like: execute_process(COMMAND ${CMAKE_COMMAND} -E copy_directory ${CMAKE_SOURCE_DIR}/test ${CMAKE_BINARY_DIR}/test COMMENT "Copying test into build directory") | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0033586) Brad King (manager) 2013-07-24 09:44 |
This is completely unnecessary. Just use message: message(STATUS "Copying test into build directory") execute_process(COMMAND ${CMAKE_COMMAND} -E copy_directory ${CMAKE_SOURCE_DIR}/test ${CMAKE_BINARY_DIR}/test) The reason add_custom_command has a COMMENT option is because that doesn't run the command but instead adds it to the generated build system, and the project files have a spot for a comment. |
|
(0034653) Robert Maynard (manager) 2013-12-02 08:51 |
Closing resolved issues that have not been updated in more than 4 months. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2013-07-24 05:22 | ycollet | New Issue | |
| 2013-07-24 09:44 | Brad King | Note Added: 0033586 | |
| 2013-07-24 09:44 | Brad King | Status | new => resolved |
| 2013-07-24 09:44 | Brad King | Resolution | open => won't fix |
| 2013-12-02 08:51 | Robert Maynard | Note Added: 0034653 | |
| 2013-12-02 08:51 | Robert Maynard | Status | resolved => closed |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |