| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| | |
d18ff3a5 WriteBasicConfigVersionFile: Fix messages in ExactVersion tests
16a93de0 WriteBasicConfigVersionFile: Add SameMinorVersion COMPATIBILITY option
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Claudio <claudio.fantacci@gmail.com>
Merge-request: !1507
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
70f9f62d GoogleTest: Fix multiple discovery on same target
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1510
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
According to the documentation, tests can be discovered for a target
multiple times by using a different prefix and/or suffix to ensure name
uniqueness. However, while this worked for gtest_add_tests, it did not
work with gtest_discover_tests because the generated file that sets up
the tests was named based only on the target name, and so subsequent
discovery from the same target would clobber earlier discovery.
Fix this by introducing a counter that records how many times discovery
has been used on a target, and use this to generate unique names of the
generated test list files.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
8e7e7af5 IRSL: Install the 1041 folder for Intel compilers
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1509
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The presence of the `1041` seems to solely depend on whether a given
Intel compiler release was available in Japanese or not. Install it if
it is present and silently ignore it otherwise.
Example: The Intel 2018.0 release did not ship it, but the 2018.1
compilers have it.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
f81d186b FindQt4: Set PLUGINS and IMPORTS dir even if empty
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1503
|
| |/ /
| | |
| | |
| | |
| | | |
Fixes: #14155
Issue: #17492
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
9b503cc8 wxWidgets: Respect WX_CONFIG and WXRC_CMD env vars
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1504
|
| |/ /
| | |
| | |
| | | |
Issue: #17492
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
35b8a26b FindImageMagick: Add more library names
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1505
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The port maintainers on FreeBSD normalize the library names to not
include the bit and HDRI options.
Furthermore, `--quantum-depth=32` and `--quantum-depth=64` will yield
`Q32` and `Q64` suffixes in the library names.
Issue: #17492
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
40434631 Autogen: Use integers instead of strings for the Qt version
be11a852 Autogen: Use project relative paths in rcc custom command comment
ab9d5896 Autogen: Detect rcc feature once during configuration
2a85b5ac Autogen: Make cmQtAutoGeneratorInitializer an instantiable class
75819b86 Autogen: Add and use cmQtAutoGenerator base class
27ed3b35 Autogen: Rename cmQtAutoGenerators to cmQtAutoGeneratorMocUic
1cd285fe Autogen: Remove rcc code from cmQtAutoGenerators
a87f82e0 Autogen: Switch to use custom commands for RCC
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1494
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We used to detect the `rcc` features before every `rcc` list invocation
wich resulted in `rcc` be called twice for every listing operation.
Now we detect the `rcc` list capabilities once during configuration and
pass it to the cmake_autorcc target in the info file.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adds the new base class `cmQtAutoGenerator` which contains common
variables and methods used by `cmQtAutoGeneratorMocUic` and
`cmQtAutoGeneratorRcc`.
|
| | | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of processing all `rcc` invocation requests in the
_autogen target that calls `cmake -E cmake_autogen ...` once,
use a dedicated custom command that calls
`cmake -E cmake_autorcc ...` for each `.qrc` file.
This allows parallel `.qrc` file processing and reduces the
workload (and complexity) in the _autogen target.
If only `AUTORCC` is enabled, the _autogen target won't be created
at all since it is now used for `AUTOMOC` and `AUTOUIC` only.
For `.qrc` files that are GENERATED a custom target is used
instead of a custom command.
Closes #17161
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
325f34d1 CPack tests: add possibility for expecting config developer warnings
176281e1 CPack test: correctly handle CPACK_PACKAGING_INSTALL_PREFIX
cf0c2599 CPack: set variable commands in lower case
2ff906b3 CPack: documentation typo fix
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1499
|
| | | | |
|
| |/ / |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
2ea17412 FindOpenGL: Add policy CMP0072 to prefer GLVND for legacy GL
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Clinton Stimpson <clinton@elemtech.com>
Merge-request: !1491
|
| | |
| | |
| | |
| | | |
Fixes: #17449
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
f5bc7826 Find{BLAS,LAPACK}: Add support for FLAME blis and libflame
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1486
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
FLAME (github.com/flame) provides a variety of numerical libraries.
`blis` and `libflame` can be setup to expose BLAS/LAPACK interfaces.
Fixes: #17470
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
cd2cdfe2 FindRuby: Add support for versions 2.2, 2.3, and 2.4
23ab451a FindRuby: Fix match of '.' in version numbers
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1493
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Author: J. Peter Mugaas (jpmugaas on gitlab.kitware.com)
Fixes: #17475
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
Escape `.` so that it is matched literally and not treated as a
special match of any character by the regex.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
36cc4378 FindOpenMP: Enable policy CMP0012
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1490
|
| |/ / /
| | | |
| | | |
| | | | |
Fixes: #17476
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
9f1916aa FindMatlab: Avoid if() auto-dereference in 64-bit host detection
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1482
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If the value of `CMAKE_HOST_SYSTEM_PROCESSOR` also happens to be set as
a variable by a project (e.g. `AMD64`), allowing `if()` to
auto-dereference is unlikely to produce a value that matches "64".
Instead let `if()` auto-dereference `CMAKE_HOST_SYSTEM_PROCESSOR`.
Fixes: #17460
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
98314d53 FindOpenMP: Use NO_DEFAULT_PATH where appropriate
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1481
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
OpenMP libraries must always be found in the implicit linking
directories of a compiler when using the OpenMP compile flag. If a suitable OpenMP library is also found in for example some CMAKE_PREFIX_PATH, this can lead to the module finding the incorrect library.
On the other hand, CMAKE_PREFIX_PATH can't ever be a location that we
need to consider since the OpenMP compile flag would not work if we
needed to.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
1615cded FindMPI: Treat 'command not found' as an error
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1483
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If the compiler given in I_MPI_... could not be found, the Intel MPI
wrappers emit an error like "line 590: ifort: command not found".
The script should currently fail to match the output of this for
information, but we should generally treat such an output as invalid,
since the displayed configuration line can become a mixup between Intel
and GNU compiler settings.
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
3bc21a70 MSVC: Fix MSVC_VERSION when mixing MSVC C/C++ with Intel Fortran
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1488
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When using a real MSVC compiler for `C` or `CXX`, use the version of
that compiler for `MSVC_VERSION`. This is preferred over the MSVC
version that a non-MSVC compiler "simulates".
Fixes: #17468
|
|\ \ \
| |/ /
|/| /
| |/
| |
| |
| |
| |
| | |
ff3c11ee FindOpenGL: Add option to prefer GLVND for legacy GL
aadc38c7 FindOpenGL: Re-order component library searches
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Clinton Stimpson <clinton@elemtech.com>
Merge-request: !1485
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since commit v3.10.0-rc5~3^2 (FindOpenGL: Default to non-GLVND libraries
for legacy GL, 2017-11-08) users may set `OPENGL_gl_LIBRARY` to empty to
use GLVND components for the legacy GL interfaces. This is useful only
when one knows in advance that the GLVND components will be found.
Add a `OpenGL_GL_PREFERENCE` variable to specify a preference for legacy
GL or GLVND. The latter can suppress `OPENGL_gl_LIBRARY` only when the
needed GLVND components are found. If no preference is explicitly
specified, choose a default based on whether GLVND components were
requested (because this indicates the project has been updated for
CMake 3.10).
Issue: #17437
Issue: #17449
|
| |
| |
| |
| |
| | |
Move the search for the legacy GL library to after the GLVND libraries.
For now we still always look for both.
|
| |\
| | |
| | |
| | | |
Merge-request: !1472
|
| |\ \
| | | |
| | | |
| | | | |
Merge-request: !1466
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
Merge-request: !1465
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
Merge-request: !1460
|
| |\ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
Merge-request: !1459
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Merge-request: !1449
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Merge-request: !1451
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
2ee10119 swig: fix incremental build in case of removed interface files
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !1457
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Commit v3.8.0-rc1~123^2 (UseSWIG: Automatically scan dependencies of SWIG files
for Makefiles, 2016-12-21) introduced automatic dependency scanning for files
`%include`d in a swig interface definition file. This works fine as long as no
such file is removed. But removing a dependent file breaks an incremental build
and `make` complains about a missing dependency, see #16830.
Integrate the approach proposed in the issue above into the SWIG-module, do the
workaround in a conditional step as it arises only for Makefile generators. For
other generators use the implementation before that commit.
Fixes: #17433.
|