James Bigler wrote:
If this feature comes to fruition, I would like the ability to specify
which flags make it into what header. In one project I worked on all
our configuration defines were in a single header. This caused
extremely long recompiles if something happened to change the one
autoheader. We eventually broke it into multiple files, and got
targeted recompiles.
I also like the idea of not having to have a configure.h.in
<http://configure.h.in> file like Hendrik Sattler suggested (put these
variables in this header here).
Do you have an API suggestion? What should this look like?
-Bill
_______________________________________________
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
