| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
6ef54e0272 CTest: add test failure reason to JUnit XML output
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8151
|
| |
| |
| |
| |
| |
| |
| |
| | |
In case of test failure, add the test failure reason (e.g. "Timeout") to
the failure message in the XML file. This is the same value that is
shown in the ctest text output.
Fixes: #24184
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
dd968ca388 cmTarget: convert VS property settings to the new property lambda
b69fba7cd7 cmTarget: factor out `POSITION_INDEPENDENT_CODE` initialization
42575a660f cmTarget: factor out properties with targets with commands
f551f49a17 cmTarget: factor out properties for targets with exports
d1627118e7 cmTarget: factor out executable-requiring properties
f0ae00d727 cmTarget: factor out linkable normal library target properties
9f7a25a2c7 cmTarget: factor out non-executable normal target with artifact properties
ab2b967ce6 cmTarget: factor out normal targets with artifact properties
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8139
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This property is initialized using the common framework, but then forced
on SHARED and MODULE targets, so just post-process the property in this
case.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This structure will encapsulate when properties are initialized within a
target.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
33e27f6ca6 <LANG>_LINKER_LAUNCHER: Allow generator expressions
84ada0b0c9 <LANG>_COMPILER_LAUNCHER: Expand subset of genexes that can be evaluated
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Merge-request: !8152
|
| | | | |
|
| | |/
| |/| |
|
| | | |
|
|\ \ \
| |_|/
|/| | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
220fa1d92b Configure CMake itself with policies through CMake 3.25
4feea27761 export: Increase maximum policy version in exported files to 3.25
1ff14d584c Add deprecation warnings for policies CMP0114 and below
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Acked-by: Alex <leha-bot@yandex.ru>
Merge-request: !8149
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The files generatd by `install(EXPORT)` and `export()` commands
are known to work with policies as of CMake 3.25, so enable them
in sufficiently new CMake versions.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The OLD behaviors of all policies are deprecated, but only by
documentation. Add an explicit deprecation diagnostic for policies
introduced in CMake 3.19 and below to encourage projects to port
away from setting policies to OLD.
|
|\ \ \ \
| | |/ /
| |/| | |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
13810dee17 cmDependsFortran: require that dependency info files work
eed295fd8a cmGlobalNinjaGenerator: require that dependency info files work
837f7c113a cmCommonTargetGenerator: classify linked target directories by language
d19648a928 cmGeneratorTarget: add a method to query if Fortran sources exist
245a89d8b6 cmMakefileTargetGenerator: make "target linked info" variable Fortran-specific
aeb1b2ae3d cmMakefileTargetGenerator: simplify string streaming
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8146
|
|\ \ \ \ \
| | |/ / /
| |/| | /
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
13810dee17 cmDependsFortran: require that dependency info files work
eed295fd8a cmGlobalNinjaGenerator: require that dependency info files work
837f7c113a cmCommonTargetGenerator: classify linked target directories by language
d19648a928 cmGeneratorTarget: add a method to query if Fortran sources exist
245a89d8b6 cmMakefileTargetGenerator: make "target linked info" variable Fortran-specific
aeb1b2ae3d cmMakefileTargetGenerator: simplify string streaming
Acked-by: Kitware Robot <kwrobot@kitware.com>
Tested-by: buildbot <buildbot@kitware.com>
Merge-request: !8146
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Now that only targets expected to have information are listed, all
`DependInfo.cmake` files should exist.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Now that only targets expected to have information are listed, all
`<LANG>Modules.json` files should exist.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These directories are used to direct collators for Fortran and C++
modules to consume dependent module information to properly collate.
However, the consumption of these files merely checks for existence of
the file, not whether they are actually needed anymore.
The problem arises when a target has Fortran or C++ modules at point A,
a build occurs populating this file, and then the target is updated to
no longer have potential modules. The `DependInfo.make` (for
`Makefiles`) or `<LANG>DependInfo.json` (for `Ninja`) files still exist
as they are never guaranteed to be cleaned up. This can introduce stale
information to the build which may cause a false-positive compilation if
a module file happens to still exist and gets found this way.
Instead, query the `linked-target-dirs` using the language in question
and only add the directory if it contains potential sources for modules
coming from the language in question.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
This variable is Fortran-specific, so clarify that through its name.
|
| | | | |
|
| |_|/
|/| | |
|
| | | |
|
|\ \ \
| | |/
| |/| |
|
| | | |
|
|/ /
| |
| |
| |
| | |
Release versions do not have the development topic section of
the CMake Release Notes index page.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
385435cf78 Help: Organize and revise 3.26 release notes
4c63f031c1 Help: Consolidate 3.26 release notes
bc1ba6d56b Help: Document experimental feature gate affecting CXX_SCAN_FOR_MODULES
71f9c1943d FindImageMagick: Fix documentation syntax in usage example
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !8148
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add section headers similar to the 3.25 release notes and move each
individual bullet into an appropriate section. Revise a few bullets.
Add a bullet for `FindImageMagick` that was accidentally left out
when its changes were made.
|
| | |
| | |
| | |
| | |
| | | |
Run the `Utilities/Release/consolidate-relnotes.bash` script to move
notes from `Help/release/dev/*` into `Help/release/3.26.rst`.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Also drop the release note for `CXX_SCAN_FOR_MODULES`, as the rest of
the C++ modules support has not yet been mentioned in release notes
(since it is still experimental).
|
|/ / |
|