Brad King wrote: > Steve, is there any reason for the restriction other than not implementing > more use cases up front?
There may be more information in the mailing list archives, but as far as I remember, yes - we wanted to be conservative because we didn't know more use-cases. Additionally, we didn't know the impact of making the feature more unrestricted. Eg - making it easy to alias imported targets means you can easily get imported target names which vary per project (Qt5::Core, Qt5::QtCore, TheQt5CoreLibrary etc) which doesn't seem useful. An desire to be able to do that may just be a mask on an underlying problem. CMake doesn't need multiple 'equally good' ways to solve the same problem. Thanks, Steve. -- 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
