You're welcome. The key to using it effectively, of course, is using it at the very bottom of the top level CMakeLists.txt file. It can only report on the targets defined so far, so if you put it in the middle somewhere, targets may be defined after you use it, and you'll miss them...
D On Saturday, July 18, 2015, Clifford Yapp <cliffy...@gmail.com> wrote: > On Fri, Jul 17, 2015 at 6:05 PM, David Cole <dlrd...@aol.com > <javascript:;>> wrote: > > Attached is a patch file of my first attempt. I can iterate some more > > on this (better testing, add docs, clarify existing docs, address > > anybody's comments, submit to stage) next week. Attached now in case > > anybody wants to try it out over the weekend. > > David, > > Awesome - thank you for doing that! (Way faster than I would have been > able to set it up). > > It may be Monday before I can put it through it's paces, but I'll > definitely give this a go and also see if I can combine it with the > SOURCES target property Brad pointed out to kill two problems with one > patch. > > I'll try to get at figuring out how to set up GLOBAL properties for > collecting various types of message outputs and prepare a patch for > that on Monday as well, unless someone else gets to it sooner. > > Cheers, > CY >
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
