Help: Clarify treatment of link flags in target_link_libraries
This commit is contained in:
parent
7246e0c2ef
commit
07bb27240f
|
@ -62,6 +62,12 @@ Each ``<item>`` may be:
|
||||||
dependencies, so they are generally safe to specify only as private link
|
dependencies, so they are generally safe to specify only as private link
|
||||||
items that will not propagate to dependents.
|
items that will not propagate to dependents.
|
||||||
|
|
||||||
|
Link flags specified here are inserted into the link command in the same
|
||||||
|
place as the link libraries. This might not be correct, depending on
|
||||||
|
the linker. Use the :prop_tgt:`LINK_FLAGS` target property to add link
|
||||||
|
flags explicitly. The flags will then be placed at the toolchain-defined
|
||||||
|
flag position in the link command.
|
||||||
|
|
||||||
* A ``debug``, ``optimized``, or ``general`` keyword immediately followed
|
* A ``debug``, ``optimized``, or ``general`` keyword immediately followed
|
||||||
by another ``<item>``. The item following such a keyword will be used
|
by another ``<item>``. The item following such a keyword will be used
|
||||||
only for the corresponding build configuration. The ``debug`` keyword
|
only for the corresponding build configuration. The ``debug`` keyword
|
||||||
|
|
Loading…
Reference in New Issue