Help: Clarify target_link_libraries treatment of flags (#15034)
Explain that link flags should not be used in transitive contexts.
This commit is contained in:
parent
f188845237
commit
8c03f15776
|
@ -18,7 +18,10 @@ If a library name matches that of another target in the project a
|
||||||
dependency will automatically be added in the build system to make sure
|
dependency will automatically be added in the build system to make sure
|
||||||
the library being linked is up-to-date before the target links. Item names
|
the library being linked is up-to-date before the target links. Item names
|
||||||
starting with ``-``, but not ``-l`` or ``-framework``, are treated as
|
starting with ``-``, but not ``-l`` or ``-framework``, are treated as
|
||||||
linker flags.
|
linker flags. Note that such flags will be treated like any other library
|
||||||
|
link item for purposes of transitive dependencies, so they are generally
|
||||||
|
safe to specify only as private link items that will not propagate to
|
||||||
|
dependents of ``<target>``.
|
||||||
|
|
||||||
A ``debug``, ``optimized``, or ``general`` keyword indicates that the
|
A ``debug``, ``optimized``, or ``general`` keyword indicates that the
|
||||||
library immediately following it is to be used only for the
|
library immediately following it is to be used only for the
|
||||||
|
|
Loading…
Reference in New Issue