View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0011156 | CMake | CMake | public | 2010-08-22 09:25 | 2011-05-02 14:46 | ||||
Reporter | Amine Khaldi | ||||||||
Assigned To | David Cole | ||||||||
Priority | normal | Severity | feature | Reproducibility | always | ||||
Status | closed | Resolution | won't fix | ||||||
Platform | OS | OS Version | |||||||
Product Version | CMake-2-8 | ||||||||
Target Version | Fixed in Version | CMake 2.8.4 | |||||||
Summary | 0011156: Directory Monitoring flag to the GLOB/GLOB_RECURSE functionality | ||||||||
Description | Hello, I would like to request a way to monitor the changes that occur to GLOB/GLOB_RECURSE lists, i.e. file removals and/or additions. Right now when you add or remove a file, you need to rerun CMake in order to get the new, updated list. The feature I request allows CMake to monitor this list, and automatically rerun CMake on the module if the list changes. Right now, to have this functionality, we're forced to include source files one by one. Having this option will have the same result, but with smaller CMakeLists files and convenience when writing them. Thank you. Regards, Amine. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0021879) Amine Khaldi (reporter) 2010-08-22 09:36 |
If it's worth mentioning, we use the MinGW Makefiles generator. |
(0024166) David Cole (manager) 2010-12-15 11:48 |
So you want CMake to run continuously in the background and monitor all changes to your source tree? Just clarifying what your expectations are. Not sure I understand how we could possibly achieve this. It seems unrealistic to me to introduce a cmake-daemon app that would monitor all known source trees even when cmake itself is not running anymore. How would we call you back? How would we notify you that your makefile is out of date? How would we know when you don't care about a particular source tree anymore, and we can stop monitoring it for changes? Would you just expect us to "touch" your CMakeLists.txt file to force a cmake re-run, or would you expect more than that? This feature request would take a major amount of work to implement. |
(0024821) David Cole (manager) 2011-01-17 16:26 |
We will not add any "directory monitoring capability" to CMake at this point in time. I think it's a beyond-the-scope-of-CMake feature request. CMake works on too many platforms to make a "directory listening daemon" a practical solution to this "problem" I think. If you have a specific proposal for a code patch that implements something you think we should do in CMake, please re-open this and attach the patch for discusssion. |
(0026356) David Cole (manager) 2011-05-02 14:46 |
Closing resolved issues that have not been updated in more than 3 months. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2010-08-22 09:25 | Amine Khaldi | New Issue | |
2010-08-22 09:36 | Amine Khaldi | Note Added: 0021879 | |
2010-12-15 11:48 | David Cole | Note Added: 0024166 | |
2011-01-17 16:24 | David Cole | Assigned To | => David Cole |
2011-01-17 16:24 | David Cole | Status | new => assigned |
2011-01-17 16:26 | David Cole | Note Added: 0024821 | |
2011-01-17 16:26 | David Cole | Status | assigned => resolved |
2011-01-17 16:26 | David Cole | Fixed in Version | => CMake 2.8.4 |
2011-01-17 16:26 | David Cole | Resolution | open => won't fix |
2011-05-02 14:46 | David Cole | Note Added: 0026356 | |
2011-05-02 14:46 | David Cole | Status | resolved => closed |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |