- 20 Nov, 2019 1 commit
-
-
Kyle Edwards authored
-
- 19 Nov, 2019 1 commit
-
-
Charles Barto authored
-
- 18 Nov, 2019 1 commit
-
-
Gregor Jasny authored
Closes: #19967
-
- 15 Nov, 2019 2 commits
-
-
Brad King authored
Combine `--repeat-until-fail`, `--repeat-until-pass`, and `--repeat-after-timeout` to create a single `--repeat <mode>:<n>` option. Retain `--repeat-until-fail` too because that has been available in previous releases.
-
Cristian Adam authored
Fixes: #19970
-
- 13 Nov, 2019 2 commits
-
-
Johnny Jazeix authored
-
Johnny Jazeix authored
-
- 11 Nov, 2019 5 commits
-
-
Alex Turbov authored
In commit da5ac4bb (cpack: Add `CPACK_INSTALL_CMAKE_CONFIGURATIONS` variable, 2019-07-10, v3.16.0-rc1~165^2) we added both the variable and support for `cpack -C` with multiple configurations. Drop the variable because the `package` target cannot ensure that all of the configurations are built. Keep the command-line interface so that it can be used manually in scripts. Fixes: #19918
-
Cristian Adam authored
Fixes: #19936
-
Cristian Adam authored
Fixes: #19946 Fixes: #19947Co-authored-by:
Craig Scott <craig.scott@crascit.com>
-
Cristian Adam authored
Fixes: #19952
- 09 Nov, 2019 1 commit
-
-
Cristian Adam authored
Fixes: #19920
-
- 07 Nov, 2019 1 commit
-
-
Brad King authored
-
- 06 Nov, 2019 2 commits
-
-
Cristian Adam authored
There is no reason to skip the generated files, in case of problems one can use the SKIP_UNITY_BUILD_INCLUSION property. Fixes: #19925
-
Alex Turbov authored
- fix the typo in `foreach` documentation - fix broken `foreach(... IN ITEMS ... LISTS ...)` - add tests of `foreach` for existed functionality and fixes
-
- 05 Nov, 2019 5 commits
-
-
Craig Scott authored
Also includes variants like hw -> res
-
Craig Scott authored
-
Craig Scott authored
Only changes the user-visible effects of renaming hardware allocation to resource allocation. Code changes are the minimum needed to achieve that.
-
Brad King authored
The `PROCESSES` test property name added for CMake 3.16 is too close to the existing `PROCESSORS` test property. Furthermore, the property in principle specifies groups of resources organized in a way that is meaningful to a particular test. The groups may often correspond to processes but they could have other meanings. Since the property name `PROCESSES` has not been in a final 3.16 release yet, simply rename it to `RESOURCE_GROUPS`. Fixes: #19914
- 04 Nov, 2019 3 commits
-
-
Kyle Edwards authored
-
- 02 Nov, 2019 2 commits
-
-
Alex Turbov authored
Closes #19638. Co-Authored-By:
Craig Scott <craig.scott@crascit.com>
-
Craig Scott authored
Fixes: #19909
-
- 01 Nov, 2019 1 commit
-
-
Brad King authored
These are not useful in nightly testing.
-
- 29 Oct, 2019 2 commits
-
-
Brad King authored
Add an option to re-run tests if they timeout. This will help tolerate sporadic timeouts on busy machines.
-
- 27 Oct, 2019 2 commits
-
-
Craig Scott authored
-
Craig Scott authored
-
- 26 Oct, 2019 1 commit
-
-
Craig Scott authored
This fixes two errors: not accounting for the trailing null and a misunderstanding of what std::numeric_limits::digits10 means.
-
- 18 Oct, 2019 1 commit
-
-
Daan De Meyer authored
Fixes: #18386
-
- 17 Oct, 2019 3 commits
-
-
Brad King authored
Since commit 97cc29c7 (VS: Teach generators how to mark per-config source files, 2017-04-10, v3.9.0-rc1~268^2~2) the VS generators have known how to generate per-config sources. We've now converted most other code paths to support per-config sources, so drop the check that disallows it. This leaves only per-config support for precompiled headers and unity build transformations, but those are optional features that can be addressed later. Fixes: #18233 Issue: #19789
-
Alexander Boczar authored
Issue: #19708
-
Alex Turbov authored
-
- 16 Oct, 2019 1 commit
-
- 15 Oct, 2019 2 commits
-
-
Alexander Boczar authored
Fixes: #19708
-
Charly Mourglia authored
Add a `VS_DOTNET_DOCUMENTATION_FILE` target property to tell VS generators to add a `DocumentationFile` setting in `.csproj` files. Fixes: #19784
-
- 14 Oct, 2019 1 commit
-
-
Peter Waller authored
Since commit 4ca0526f (cmake: Pass -S and -B into PreLoad.cmake and -C scripts, 2019-08-20, v3.16.0-rc1~195^2) the value of `CMAKE_SOURCE_DIR` is the source directory rather than the current working directory. This was correct on its own, but the place storing that value is also used as the base for relative paths specified on the command line. The latter should of course be relative to the current working directory. The fix is to switch to use a full path internally, unless a full path is already specified. Add tests for the behaviour of `-C` under these four circumstances: {with -S, without -S} x {full path, relative path} Fixes: #19827
-