On Wed, Feb 10, 2016 at 12:12 AM, Stephen Kelly <steve...@gmail.com> wrote: > 3) Compute cmGeneratorTarget state non-lazily in its constructor. > * Historically target state for generators was computed lazily because it > might need to be cleared and re-computed. That is no-longer true.
SourceFilesMap is cleared in a call to AddSource. It is then recomputed the next time GetSourceFiles is called. > * For example, the LinkInformation is populated lazily in > cmGeneratorTarget::GetLinkInformation. > * Instead the LinkInformation could be populated in the cmGeneratorTarget > constructor for all known configurations. That is what generators will > request during generate-time anyway. > * Doing this will make it possible to split a cmComputedTarget out of > cmGeneratorTarget. I started splitting out a cmComputedTarget. It is initialized in its constructor for one single configuration. The entries of the ComputedTargets map are computed and recomputed lazily because of the reason mentioned above. Please review: https://github.com/purpleKarrot/CMake/commits/computed-target -- 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
