| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Xcode 5.0 now computes dependencies from files linked through
OTHER_LDFLAGS, so we no longer need the XCODE_DEPEND_HELPER hack to
re-link dependents when targets change.
|
| |
|
|\
| |
| |
| |
| | |
dccd494 Use first custom command for the same output (#14446)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In buggy code like
add_custom_command(
OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/out.h
MAIN_DEPENDENCY ${CMAKE_CURRENT_SOURCE_DIR}/out.h.in
...)
add_custom_command(
OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/out.h
...)
that has more than one rule to generate the same output CMake has always
used the first rule. However, since commit 2268c41a (Optimize custom
command full-path dependency lookup, 2013-08-06) we update the map from
output to cmSourceFile for every rule generating an output, effectively
keeping the last command instead of the first.
Fix this regression by checking for each map update if the output
already has an entry. If so, keep only the original entry. The VS 8
generator triggers this with a special case for generate.stamp rules
that differ between ZERO_CHECK and normal targets, so do not warn for
now. Leave a TODO comment for warning in the future.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
70089d0 genex: Fix preprocessing with incomplete content (#14410).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Similar incomplete generator expressions are already tested
in the GeneratorExpression unit test, but those are executed
with add_custom_target. The generator expressions in the include
directories are run through the preprocessor, whereas the ones
run through add_custom_target are not.
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
271bf10 Fix CMP0022 warning when no old-style property is set
|
| | |
| | |
| | |
| | | |
The string could be null at this point.
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
81d2793 Add differing target property content to policy CMP0022 warning
|
| | |
| | |
| | |
| | |
| | | |
List the contents of the INTERFACE_LINK_LIBRARIES and the old-style
property.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
cd90a0e VS: Future-proof Intel project format selection
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The version of Intel Fortran that actually uses 9.10 as a project format
is very old. Default to the latest format version (11.0) and use the
older format only when known to be necessary.
Suggested-by: Dick Munroe <munroe@csworks.com>
|
| |/ /
|/| | |
|
|/ / |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
38571f2 cmMakefile: Do not track CMake temporary files.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since commit ad502502 (cmMakefile: Track configured files so we can
regenerate them, 2013-06-18) cmMakefile::ConfigureFile records the
configured file as an output file generated by CMake. The intention is
that for make and ninja we can re-run CMake when one of the files it
generates goes missing. However, files configured temporarily in
CMakeTmp directories by Check* modules do not live past the CMake
invocation.
We have to also track input files to the configure command. In theory
the input to a configure command could it self be a file that is going
to be deleted later (output from a custom command or configure_file).
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
782eba3 CTest: Fix GTM coverage parsing line offset bug
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In cmParseGTMCoverage::ReadMCovFile, initialize the lineoffset variable.
Also set lastoffset only if the function is found (thanks to Bill
Hoffman).
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
5e15f39 Normalize system directories from the interface target property
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The input dir being tested is normalized, so ensure that the entries
in the vector are normalized too (eg no trailing slash).
|