I'm now at the point in writing CMake logic where I need to handle the config.h.in situation, and either have missed the autoheader equivalent functionality in CMake or it doesn't exist yet. Can anybody point me to the "right" approach to this? I have so-far found:
The #cmakedefine mechanism and the various CHECK_* functions, which work fine but aren't autogenerated a.l.a autoheader A 2009 discussion about autoheader-style functionality: http://www.cmake.org/pipermail/cmake/2009-March/028293.html http://www.cmake.org/pipermail/cmake/2009-April/028417.html and a still-open item in the tracker from 2008: http://www.cmake.org/Bug/view.php?id=6438&nbn=1 Has there been any recent work on this that I missed? Our project has quite a slew of these #defines created by autoheader, most of which are apparently actually needed, so manually maintaining a list is gonna be a bit of a tough sell. Cheers, and any help appreciated, CY _______________________________________________ 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
