Stephen Kelly wrote: > > Hi there, > > The topic of 'target usage requirements' has come up several times. It's > something I'd like to work further towards in CMake 2.8.9. > > I have created a wiki page on the KDE wiki (there for my convenience > mostly) so that we can discuss the design, implementation and > implications. > > http://community.kde.org/Frameworks/Epics/CMake_target_usage_requirements > > Thanks for any comments,
Hi there, Thanks for the feedback on this proposal so far. I have updated the wiki page to remove any reference to target_use_package() or functionality depending on conventions of variable names, or finding packages etc. The proposal as written now expects the caller to supply targets, and never expects a package name or a prefix. The page is now focussed on creation of a target_use_targets() command which operates on targets which are in scope because either they were created in the same buildsystem, or they were imported. It would be possible to revisit the target_use_package() idea in the future, but that is no longer the aim of the proposal. The target_use_targets() is already a useful enough concept to aim for. The remaining (I think) open question regards what form the generator expressions should take so that they can represent multiple dimensions. Thanks, Steve. -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
