On Wed, Jul 15, 2015 at 9:10 AM, Brad King <brad.k...@kitware.com> wrote: > On 07/10/2015 03:42 PM, Clifford Yapp wrote: >> On Thu, Jul 9, 2015 at 1:35 PM, Clifford Yapp <cliffy...@gmail.com> wrote: >> >>> 2. Provide similar lists of all defined targets for the various types >>> (e.g. CMAKE_EXECUTABLE_TARGETS, CMAKE_LIBRARY_TARGETS, >>> CMAKE_CUSTOM_TARGETS). >> >> Looking into the CMake sources, it seems like this information is >> stored already in the global target map - what would be the "correct" >> way to expose that information in variables in CMake script space? > > We shouldn't need separate lists for each because one can check > the TYPE target property given the target name.
Ah, good point. > The list of globally-scoped (non-imported) targets could be made available > through a (read-only) global property whose implementation > computes the list on the fly. Sounds workable - are there any pre-existing properties like that that can serve as a guide for implementation? Thanks, 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
