Eric Noulard said the following on 11/14/2010 4:00 AM:
I do (may be did?) have mental dichotomy between the "build process"
I'm going to take blame there for doing a poor job of posing the
original inquiry :)
But may be I shall step back and just think differently about it and even if
I need to explicitly use SCM for headers may be they shall just "disappear"
from CMakeLists.txt?
May be the public "exported" headers would still appear in the CMakeLists.txt
but most of them can just go away.
I don't think there is a globally quantifiable way to distinguish
exportable headers, so that is a distinct data point (the same way that
for many projects "*/*.cpp" isn't an accurate description of the source
dependencies for any given target :)
Now re-reading the Michael post it seems that having some hook
(or property)
to get dependency list from a particular file (or target) should be
the way to go.
Yep, I was thinking the same. I'll look at writing a feature request, as
you suggest :)
- Oliver
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
