| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
An empty string is not likely going to produce expected results
in any evaluation context. It is replaced by preprocessing
currently.
|
|
|
|
|
|
| |
When evaluating TARGET_PROPERTY here, we can skip to the comma
location. We need to calculate it though as the string may have
just been changed.
|
|
|
|
| |
This was segfaulting before.
|
|\
| |
| |
| |
| |
| |
| | |
7bf490e Make subclasses responsible for joining content.
f6b16d4 Don't allow targets args in the new target commands.
b3a7e19 Make the Property name protected so that subclasses can use it.
|
| |
| |
| |
| |
| | |
This way we can add handling of relative/absolute paths and of
-D in compile definitions.
|
| | |
|
| |
| |
| |
| | |
Makes subclasses more dry in upcoming patches.
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
5daaa5c Fix TARGET_PROPERTY target extractions.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We need to make sure we can export targets which have content such
as $<0:$<TARGET_PROPERTY:not_a_target,INTERFACE_INCLUDE_DIRECTORIES>
That means making not finding a target non-fatal here.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
a7d6ebb documentation: handling of relative paths by include- and link_directories()
|
| | | |
| | | |
| | | |
| | | | |
Alex
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
34d1ade Add the INSTALL_PREFIX genex.
3a17197 Generate the _IMPORT_PREFIX in the non-config export file.
|
| | | | | |
|
| |/ / / |
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | | |
429e369 Process COMPILE_DEFINITIONS as generator expressions in QtAutomoc.
0e10782 Move GetCompileDefinitions to cmTarget.
|
| | | |
| | | |
| | | |
| | | | |
Fixes #13493.
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
|/| | |
|
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | | |
6c57c31 doc: fix linebreaks in generator expression documentation
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | | |
f032fb9 target_link_libraries: Document that new sigs privatize old (#13876)
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Explain in the documentation for the legacy signature
target_link_libraries(foo bar)
that the other signatures like
target_link_libraries(foo LINK_INTERFACE_LIBRARIES ...)
target_link_libraries(foo LINK_PRIVATE ...)
will set the LINK_INTERFACE_LIBRARIES target property and therefore make
libraries specified only by the legacy signature private.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
2fb2c32 Add the COMPATIBLE_INTERFACE_STRING property.
cd66b91 Make calculation of link-interface-dependent properties type-sensitive.
|
| | | |
|
| |/ |
|
|/ |
|
|\
| |
| |
| |
| | |
6fbe3ce Exclude the LINK_LIBRARIES related properties from INTERFACE evaluation.
|
| |
| |
| |
| |
| |
| | |
These interface-related link-libraries properties are used to determine
the value of the other INTERFACE properties, so we were getting infinite
recursion and segfaults otherwise.
|
|\ \
| | |
| | |
| | |
| | | |
3853a6c spell: fix a few typos in comments
|
| | | |
|
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
b98d14d Disallow porcelain to populate includes and defines of IMPORTED targets.
48a4cf2 Revert "Allow target_link_libraries with IMPORTED targets."
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With similar reasoning to the parent commit, as downstreams, we can't
determine what $<CONFIG> generator expressions would be appropriate.
Upstream would have populated the INTERFACE_INCLUDE_DIRECTORIES with
config-specific generator expressions, possibly appropriate for
their DEBUG_CONFIGURATIONS. In theory, if we would add include
directories for a DEBUG intent, we would have to match the upstream
configurations for that.
Rather than attempting to discover the appropriate configurations
at this time, simplify the feature instead. The use of IMPORTED targets
with these commands could still be added in the future if targets
would export their DEBUG_CONFIGURATIONS somehow.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 9cfe4f1b769597bd9ba179eba46572a9df27f64c.
It turns out that correctly adding the content to
the IMPORTED_LINK_INTERFACE_LIBARIES_<CONFIG> of an upstream target
from the buildsystem of a downstream project is not simple.
If upstream had added the INTERFACE content, the config-specific
properties would be determined by the DEBUG_CONFIGURATIONS of
upstream.
As downstream, we don't have any information about what
the DEBUG_CONFIGURATIONS of upstream were, so we can't determine
which configuration-specific properties to populate. The best we can do
is add it to all of them or add it to the ones downstream considers to
be DEBUG_CONFIGURATIONS, neither of which is a good solution.
So, removing the porcelain API for that is the best approach. A human
can still determine which properties to populate and use
the set_property API to populate the desired properies.
Another solution to this would be for upstream targets to publish
what they consider DEBUG_CONFIGURATIONS, but that can be added in
a future release.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
6063fef Output include directories as LOG messages, not warnings.
aa66748 Specify the target whose includes are being listed.
d70204a Only output includes once after the start of 'generate-time' when debugging.
0d46e9a Store includes from the same include_directories call together.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
During configure-time, GetIncludeDirectories may be called too, for example
if using the export() command. As the content can be different, it should
be output each time then.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise, we get a separate IncludeDirectoriesEntry for each include,
and that causes unnecessary and confusing splitting in the output when
debugging the INCLUDE_DIRECTORIES property.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
02d4e53 Generate new-style cmake code during export.
|
| | | |
| | | |
| | | |
| | | | |
Use empty end*() commands and lowercase commands.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
d7f1520 Don't wrap all targets in LINK_LIBRARIES in a TARGET_NAME genex.
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It is not necessary and the current state is unintentional. Before
this patch,
target_link_libraries(foo bar)
causes the LINK_LIBRARIES property of foo to contain
$<TARGET_NAME:bar>
instead of just
bar
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
e3b5eb6 Automatically link to the qtmain library when linking to QtCore.
6c8d8af Add the $<TARGET_POLICY> expression
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When using QAxServer, ensure that the qtmain library is excluded
by reporting an error at CMake time if it is not.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This new expression allows checking how a policy was set when a target
was created. That information is only recorded for a subset of policies,
so a whitelist is used.
|