On 07/29/2013 06:39 AM, Stephen Kelly wrote:
> So, I don't think it should be an error to specify INCLUDE DESTINATION
> without EXPORT. After all, I can specify LIBRARY DESTINATION for
> executables...
Okay, that makes sense. Yes, I think we can leave out the error.
-Brad
--
Powered by www.ki
Brad King wrote:
> Please add an error condition when INCLUDES DESTINATION is used
> without EXPORT and a test case to cover it.
I added that, but I think it would be better to remove the error case.
In KDE we have a INSTALL_TARGETS_DEFAULT_ARGS variable, used like this:
install(TARGETS klib1
On 07/15/2013 02:00 PM, Stephen Kelly wrote:
> Brad King wrote:
>
>> On 7/15/2013 11:25 AM, Stephen Kelly wrote:
>>> The solution I think is to add the specified include directories to the
>>> cmTargetExport instance which gets created when using the EXPORT, and to
>>> append the directories only
Brad King wrote:
> On 7/15/2013 11:25 AM, Stephen Kelly wrote:
>> The solution I think is to add the specified include directories to the
>> cmTargetExport instance which gets created when using the EXPORT, and to
>> append the directories only when generating.
>
> Yes, certainly the INCLUDES DES
On 7/15/2013 11:25 AM, Stephen Kelly wrote:
> The solution I think is to add the specified include directories to the
> cmTargetExport instance which gets created when using the EXPORT, and to
> append the directories only when generating.
Yes, certainly the INCLUDES DESTINATION needs to be asso
Brad King wrote:
> Steve,
>
> From the documentation of the feature:
>
> + "The INCLUDES DESTINATION specifies a list of directories which
> will "
> + "be added to the INTERFACE_INCLUDE_DIRECTORIES of the
> when "
> + "exported by install(EXPORT). If a relative path is specifie
Steve,
>From the documentation of the feature:
+ "The INCLUDES DESTINATION specifies a list of directories which will "
+ "be added to the INTERFACE_INCLUDE_DIRECTORIES of the when "
+ "exported by install(EXPORT). If a relative path is specified, it is "
+ "treated as relat
