[cmake-developers] Target usage requirements and conventions

[Stephen Kelly]

Clinton Stimpson wrote:

> 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()?
> 

This isn't strictly only for imported targets, in my view.

I've updated the wiki page to make that more explicit.

http://community.kde.org/index.php?title=Frameworks%2FEpics%2FCMake_target_usage_requirements&action=historysubmit&diff=20688&oldid=20582

Thanks,

Steve.