| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since commit a13a5c948e (Replace use of CollapseCombinedPath with
CollapseFullPath, 2019-03-19, v3.15.0-rc1~361^2~1), one code path now
calls `CollapseFullPath` with a base path that may be relative.
Backport KWSys commit c6f8e24a3 (SystemTools: Fix CollapseFullPath with
relative base path, 2019-07-24) to handle such base paths.
This case occurs when a build tree is placed in a directory inside a
source tree such that CMake is willing to generate a relative path from
the build tree to the source tree. Add a test covering this case.
Fixes: #19507
|
| |
|
|\
| |
| |
| | |
Merge-request: !3557
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The module mode fallback added by commit 22e65d10c1 (find_package: Fixed
CMAKE_FIND_PACKAGE_PREFER_CONFIG Module fallback, 2019-06-13,
v3.15.0-rc2~6^2) should not be used unless the `find_package` call
allows module mode. Doing so can lead to infinite recursion if a find
module tries to call config mode with `find_package(... NO_MODULE)`.
Fix the logic and add a test case.
Fixes: #19478
|
|\ \
| | |
| | |
| | | |
Merge-request: !3549
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now that the working directory is in the build tree, relative input
paths must be converted to an absolute path to remain relative to the
source directory.
Fixes: #19472
|
|\ \ \
| | | |
| | | |
| | | | |
Merge-request: !3537
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
In commit 3a53005f7d (Build object library targets in VS, 2012-03-12,
v2.8.8~29^2~13) we updated the condition for unicode but accidentally
left out the SBCS case support for object libraries.
Fixes: #19469
|
|\ \ \
| |/ /
|/| |
| | | |
Merge-request: !3504
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Define `CMAKE_Fortran_SUBMODULE_{SEP,EXT}` for the Cray Fortran
compiler. Use an empty separator to tell CMake that this compiler does
not use the enclosing module name as a prefix on submodule files.
Issue: #18925
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Define `CMAKE_Fortran_SUBMODULE_SEP` with an empty string to mean that
the compiler uses no module prefix on its submodule files.
Also add a default fallback to use the `.mod` extension when
`CMAKE_Fortran_SUBMODULE_EXT` is not set. This is a better guess than
no extension at all.
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
Merge-request: !3532
|
| |\ \ \ |
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | | |
Update parsing logic from commit 5990ecb741 (Compute implicit include
directories from compiler output, 2018-12-07, v3.14.0-rc1~108^2)
to handle the quoting behavior caused by the `-hlist=` flag.
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Merge-request: !3526
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
This ability was lost in commit 81b4d10d8f (CUDA: More exhaustive checks
to determine when to do device linking, 2019-05-09, v3.15.0-rc1~82^2)
and needs to be restored to use imported static libraries that have CUDA
symbols.
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Merge-request: !3523
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Merge-request: !3529
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In `ccmake` a single global generator instance may be used for multiple
configure step runs. The `cmGlobalGenerator::ClearGeneratorMembers`
method is supposed to clear global state that is specific to each
configure run but forgot to clear alias targets.
Fixes: #19457
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Merge-request: !3510
|
| |/ / / |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Merge-request: !3521
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The message() command requires uppercase log levels. Even
though the cmake --loglevel option is not case sensitive, show
the supported values as uppercase to match the message()
docs as closely as possible, since they are related to the same
feature.
Also fixes the wrong string being shown for the warning level
by cmake --help.
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Merge-request: !3498
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It isn't yet clear whether we want to make this part of the
documented API for the install script. Remove it from the
docs before it appears in an official release for now.
Relates: #18997
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Merge-request: !3505
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since commit 368bcba28a (FindPostgreSQL: Find debug lib, imported
configs, 2019-05-09, v3.15.0-rc1~93^2) the `PostgreSQL_LIBRARY` variable
may contain a list and therefore should not be passed to the
`get_filename_component` command directly. Instead spell out the logic
to compute `PostgreSQL_LIBRARY_DIR` from one of the per-configuration
variables.
Fixes: #19444
|
|\ \ \ \
| |_|/ /
|/| | |
| | | | |
Merge-request: !3495
|
|/ / /
| | |
| | |
| | | |
Fixes: #19390
|
|\ \ \
| | | |
| | | |
| | | | |
Merge-request: !3500
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
`QPalette::Foreground` is deprecated and was replaced by
`QPalette::WindowText` since at least Qt 4.8.
https://doc.qt.io/archives/qt-4.8/qpalette.html#ColorRole-enum
This replaces the `QPalette::Foreground` color role with `QPalette::WindowText`
in `QtDialog/RegexExplorer.cxx` to avoid compiler warnings.
|
| |/ /
| | |
| | |
| | |
| | | |
Avoid the invalid compression level 0 when invoking rcc.
It let's rcc fail with an error since Qt 5.13.
|
|\ \ \
| | | |
| | | |
| | | | |
Merge-request: !3501
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
* upstream-expat:
expat 2019-06-19 (d3b78b42)
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Code extracted from:
https://github.com/libexpat/libexpat.git
at commit d3b78b42a2dcdea98e22625cfff67a49d47e6025 (R_2_2_7).
|
| | |/ /
| |/| | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Merge-request: !3491
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Checks added in commit 81b4d10d8f (CUDA: More exhaustive checks to
determine when to do device linking, 2019-05-09, v3.15.0-rc1~82^2)
assumed that CUDA properties would be set only if CUDA is enabled.
We cannot do a device link step if we do not have the CUDA language
enabled. This was discovered as some projects unconditionally set CUDA
properties such as `CUDA_RESOLVE_DEVICE_SYMBOLS` even when the CUDA
language has not been enabled.
Fixes: #19432
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Merge-request: !3494
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The docs for CMAKE_PROJECT_<projName>_INCLUDE and
CMAKE_PROJECT_INCLUDE did not define the order of
inclusion if both were set.
|
| |/ / / |
|
|\ \ \ \
| |/ / /
|/| | |
| | | | |
Merge-request: !3497
|
|/ / /
| | |
| | |
| | | |
Fixes: #19436
|
| | | |
|