[cmake-developers] INTERFACE_INCLUDE_DIRECTORIES on STATIC libs

Stephen Kelly steveire at gmail.com
Fri Feb 8 14:36:17 EST 2013


Brad King wrote:

> On 02/08/2013 01:46 PM, Stephen Kelly wrote:
>> I think it might make sense to handle them particularly in LINKED, but I
>> notice set_property and set_target_properties also work fine with them
>> (should that be changed too?)
> 
> The ExternalProject module makes heavy use of properties on custom
> targets.
> It is common.  It's just INTERFACE properties that do not make sense.

Ok, implemented for the LINKED expression.

> 
>>, so I don't know if TARGET_PROPERTY should be
>> changed too. If it is, then it makes sense to change TARGET_DEFINED to
>> consider utilities to not be targets, as that expression is most usefully
>> used with TARGET_PROPERTY.
> 
> Perhaps TARGET_DEFINED is not a good name then.  What are we really
> asking?  TARGET_LINKABLE?

That may not be a good name either. It reads generic enough to me to also 
mistake it as accepting libraries.

 $<TARGET_LINKABLE:foo> # Is libfoo.so available in the places 
                        # where cmake looks for it?

I don't really have a better idea at the moment though.

Thanks,

Steve.





More information about the cmake-developers mailing list