On Fri, Jul 30, 2010 at 1:45 PM, Ryan Pavlik <rpav...@iastate.edu> wrote: > If you want to avoid code duplication, write a cmake module that does it > then share it with the world. This doesn't have to be a top-down solution: > if you think you have the best library decoration system wrapped in a tidy, > documented module, then there's nothing stopping you from publicizing it and > encouraging projects (instead of project tools) to use it. De-facto, not > de-jure. > > (In general, this is my approach to things I'd like CMake to do that it > doesn't yet, and really, if it doesn't need a core change to be possible, > it's probably the best place for the code. Look in any of my projects on > GitHub, like http://github.com/rpavlik/physical-modeling-utilities , for: > > CreateLaunchers.cmake > CreateDashboardScripts.cmake > CppcheckTargets.cmake > DoxygenTargets.cmake > SetDefaultBuildType.cmake > EnableExtraCompilerWarnings.cmake > > to get an idea of how I solve these things - I solve them once in a module, > which makes its way into open source code, and hopefully if folks want to do > similar things they end up finding these modules, and/or even improving > them...)
Thanks, I'll have a look. Olaf _______________________________________________ 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
