You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@celix.apache.org by "Pepijn Noltes (JIRA)" <ji...@apache.org> on 2017/11/29 19:40:00 UTC
[jira] [Updated] (CELIX-417) Make Celix CMake target exportable
[ https://issues.apache.org/jira/browse/CELIX-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pepijn Noltes updated CELIX-417:
--------------------------------
Component/s: Build Env
> Make Celix CMake target exportable
> -----------------------------------
>
> Key: CELIX-417
> URL: https://issues.apache.org/jira/browse/CELIX-417
> Project: Celix
> Issue Type: Improvement
> Components: Build Env
> Affects Versions: 2.2.0
> Reporter: Pepijn Noltes
> Assignee: Pepijn Noltes
>
> Currently the advisable way to use CMake it to export targets and use the imported targets in project using - in this case - Celix.
> This would mean that if Celix export a target Celix::framework, the using project can add the correct link libraries, include paths and even compile definitions by using target_link_libraries. For example
> target_link_libraries(foo PRIVATE Celix::framework)
> This is also has many benefits for Celix:
> - easier in use.
> - more modern use of CMake.
> - more modular use of CMake.
> - no of almost no use of directories outside a target dir.
> - Celix examples can be used 1 on1 in project using Celix
> For more info see: https://www.youtube.com/watch?v=bsXLMQ6WgIk
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)