2013-10-15 19:17:36 +04:00
|
|
|
INTERFACE_INCLUDE_DIRECTORIES
|
|
|
|
-----------------------------
|
|
|
|
|
2014-11-22 14:30:32 +03:00
|
|
|
.. |property_name| replace:: include directories
|
|
|
|
.. |command_name| replace:: :command:`target_include_directories`
|
|
|
|
.. |PROPERTY_INTERFACE_NAME| replace:: ``INTERFACE_INCLUDE_DIRECTORIES``
|
|
|
|
.. |PROPERTY_LINK| replace:: :prop_tgt:`INCLUDE_DIRECTORIES`
|
|
|
|
.. |PROPERTY_GENEX| replace:: ``$<TARGET_PROPERTY:foo,INTERFACE_INCLUDE_DIRECTORIES>``
|
|
|
|
.. include:: INTERFACE_BUILD_PROPERTY.txt
|
2014-06-02 18:30:49 +04:00
|
|
|
|
|
|
|
Include directories usage requirements commonly differ between the build-tree
|
|
|
|
and the install-tree. The ``BUILD_INTERFACE`` and ``INSTALL_INTERFACE``
|
|
|
|
generator expressions can be used to describe separate usage requirements
|
|
|
|
based on the usage location. Relative paths are allowed within the
|
|
|
|
``INSTALL_INTERFACE`` expression and are interpreted relative to the
|
|
|
|
installation prefix. For example:
|
|
|
|
|
|
|
|
.. code-block:: cmake
|
|
|
|
|
2014-11-22 14:56:53 +03:00
|
|
|
target_include_directories(mylib INTERFACE
|
2014-06-02 18:30:49 +04:00
|
|
|
$<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/include/mylib>
|
|
|
|
$<INSTALL_INTERFACE:include/mylib> # <prefix>/include/mylib
|
2014-11-22 14:56:53 +03:00
|
|
|
)
|
2014-11-22 15:16:05 +03:00
|
|
|
|
|
|
|
.. |INTERFACE_PROPERTY_LINK| replace:: ``INTERFACE_INCLUDE_DIRECTORIES``
|
|
|
|
.. include:: /include/INTERFACE_INCLUDE_DIRECTORIES_WARNING.txt
|