On Thursday, May 03, 2012 10:21:10 am Stephen Kelly wrote: > On 05/03/2012 06:19 PM, Ben Boeckel wrote: > > On Thu, May 03, 2012 at 09:35:44 -0600, Clinton Stimpson wrote: > >> The include, defines, etc... can be properties on a target when when > >> target_use_target() is used, it could extract those properties and apply > >> them on the using target. > > > > So we'll also need a way to define private values for these things as > > well. Linking some abstraction library should not automatically link the > > abstracted library, add its header path, or add any defines for it to > > targets that use the abstraction library. > > > > --Ben > > You guys should read the wiki page :) You're a few months behind the > discussions that have already happened.
:) But I don't see anything in the wiki about using this functionality without a find_package(). If I have a large project with many shared libraries, can I use this concept you are developing to help manage the compile flags for my own libraries within my own project? Or is this strictly for imported targets/find_package()? -- Clinton Stimpson Elemental Technologies, Inc Computational Simulation Software, LLC www.csimsoft.com -- 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
