Brad King 87f44b7525 Fix export of STATIC library PRIVATE non-target dependencies
In commit v3.5.0-rc1~43^2 (Fix export of STATIC library PRIVATE
dependencies with CMP0022 NEW, 2016-01-15) we taught
target_link_libraries to generate `$<LINK_ONLY:$<TARGET_NAME:dep>>` in
INTERFACE_LINK_LIBRARIES instead of `$<LINK_ONLY:dep>` so that `dep` can
be recognized as a target name and updated during export.  However, this
approach does not work when `dep` is just a plain library name and not a
target because `$<TARGET_NAME:...>` requires the name of a reachable
target.

Since we do not know during target_link_libraries whether the name will
correspond to a reachable target or not, we cannot inject the
`$<TARGET_NAME:...>` expression.  Revert this change and solve the
original problem instead by teaching the export logic to recognize and
update target names directly in `$<LINK_ONLY:...>` expressions.

Reported-by: Ben Boeckel <ben.boeckel@kitware.com>
2016-02-17 14:01:11 -05:00
..
2015-12-18 10:02:07 -05:00
2015-12-18 10:02:07 -05:00
2015-07-23 15:33:10 -04:00
2016-02-02 00:01:05 -05:00
2015-12-18 10:02:07 -05:00
2014-10-15 23:16:44 +02:00
2014-10-15 23:16:44 +02:00
2015-11-25 10:33:26 -05:00
2015-02-20 21:36:58 +01:00
2015-06-07 09:32:24 +02:00
2015-10-28 08:48:08 -04:00
2015-05-19 22:36:51 +02:00
2015-04-13 11:44:15 -04:00
2015-12-18 10:02:07 -05:00
2015-10-26 22:30:13 +01:00