target_link_directories(<target> [BEFORE] <INTERFACE|PUBLIC|PRIVATE> [items1...] [<INTERFACE|PUBLIC|PRIVATE> [items2...] ...])
Specifies the paths in which the linker should search for libraries when linking a given target. Each item can be an absolute or relative path, with the latter being interpreted as relative to the current source directory. These items will be added to the link command.
PRIVATE keywords are required to specify the scope of the items that follow them.
PUBLIC items will populate the
LINK_DIRECTORIES property of
INTERFACE items will populate the
INTERFACE_LINK_DIRECTORIES property of
<target> (IMPORTED targets only support
INTERFACE items). Each item specifies a link directory and will be converted to an absolute path if necessary before adding it to the relevant property. Repeated calls for the same
<target> append items in the order called.
BEFORE is specified, the content will be prepended to the relevant property instead of being appended.
target_link_directories may use “generator expressions” with the syntax
$<...>. See the
cmake-generator-expressions(7) manual for available expressions. See the
cmake-buildsystem(7) manual for more on defining buildsystem properties.
This command is rarely necessary and should be avoided where there are other choices. Prefer to pass full absolute paths to libraries where possible, since this ensures the correct library will always be linked. The
find_library() command provides the full path, which can generally be used directly in calls to
target_link_libraries(). Situations where a library search path may be needed include:
RPATHmechanisms, but some linkers are not able to fully decode those paths (e.g. due to the presence of things like
© 2000–2019 Kitware, Inc. and Contributors
Licensed under the BSD 3-clause License.