summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'fix-csharp-target-type' into release-3.12Brad King2018-10-025-6/+21
|\ | | | | | | Merge-request: !2427
| * CSharp: Fix regression in VS project type selectionBrad King2018-10-024-3/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A that target contains only `.cs` sources should be generated as a `.csproj` project even if it links to non-CSharp static libraries. The latter case was broken by refactoring in commit v3.12.0-rc1~160^2~7 (remove TargetIsCSharpOnly() and use methods from cmGeneratorTarget, 2018-03-19). The reason is that the `HasLanguage` method added by commit v3.12.0-rc1~239^2~6 (cmGeneratorTarget: add HasLanguage() as wrapper for GetLanguages(), 2018-03-19) enforces its "exclusive" check on the combined set of source file languages and the link language. To restore the original `TargetIsCSharpOnly` semantics, update `HasLanguage` to enforce exclusiveness only on the list of sources. Fixes: #18239
| * VS: Fix CSharp flag selection when linking to a static C++ libraryBrad King2018-10-021-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When a CSharp target links to a static C++ library, CMake will compute the link language as C++ instead of CSharp. That may be incorrect and needs further investigation, but it does not affect how VS drives C# linking. However, it does break our flag language selection logic and causes C++ flags to be used for CSharp. In particular, this drops the `-platform:x86` flag on 32-bit builds. Fix this by always selecting the CSharp flags when generating a `.csproj` project type. Issue: #18239
* | Merge branch 'libuv-gnu-hurd' into release-3.12Brad King2018-10-011-8/+39
|\ \ | | | | | | | | | Merge-request: !2422
| * | libuv: do not require PATH_MAX to be definedBrad King2018-10-011-8/+39
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some platforms (e.g. GNU/Hurd) do not define PATH_MAX. Add a few other variants and a fallback constant. Also use alternatives where possible: * For readlink(), use lstat() to read the length of the link first. If it is not a symlink, report EINVAL before trying to allocate. If the size reports as zero, fall back one of the PATH_MAX variants. * For realpath(), POSIX 2008 allows us to pass a NULL buffer to tell it to malloc() internally. This patch was inspired by downstream patches in Debian packaging for issues 897061 and 909011. Issue: #18337
* | Merge branch 'libarchive-libressl-2.7' into release-3.12Brad King2018-09-261-1/+2
|\ \ | | | | | | | | | Merge-request: !2416
| * | libarchive: Backport fix for build with LibreSSL 2.7Brad King2018-09-261-1/+2
| |/ | | | | | | | | | | | | | | Backport libarchive commit v3.3.3~16^2 (fix build with LibreSSL 2.7, 2018-04-01). LibreSSL 2.7 adds OpenSSL 1.1 API leading to conflicts on method names. Fixes: #18404
* | Merge branch 'doc-updates' into release-3.12Brad King2018-09-191-1/+1
|\ \ | | | | | | | | | Merge-request: !2401
| * | Help: TESTS property: clarify usage.Marc Chevrier2018-09-191-1/+1
| |/
* | Merge branch 'FindDoxygen-CMP0057' into release-3.12Brad King2018-09-111-0/+5
|\ \ | | | | | | | | | Merge-request: !2373
| * | FindDoxygen: Ensure policy settings allow use of IN_LISTBrad King2018-09-111-0/+5
| |/ | | | | | | | | | | | | | | | | | | In commit v3.9.0-rc1~55^2 (Improve Doxygen support, 2017-04-10) use of the `IN_LIST` condition was added, but this is only supported when policy CMP0057 is set to NEW. Add a policy scope around the module and enable the policy within it. Otherwise it works only in projects that happen to enable the policy. Fixes: #18361
* | Merge branch 'FindMPI-restore-flags-string' into release-3.12Brad King2018-09-101-1/+1
|\ \ | | | | | | | | | Merge-request: !2368
| * | FindMPI: Restore MPI_<LANG>_COMPILE_FLAGS as a command-line stringBrad King2018-09-101-1/+1
| |/ | | | | | | | | | | | | | | | | Refactoring in commit v3.10.0-rc1~103^2~2 (FindMPI: Modernization from ground up, 2017-04-25) accidentally left this variable set as a copy of the `;`-list in `MPI_<LANG>_COMPILE_OPTIONS`, but the flags variable is documented as a command-line string. Restore it now. Fixes: #18349
* | Merge branch 'fix-ctest_start-track' into release-3.12Brad King2018-09-104-3/+14
|\ \ | | | | | | | | | Merge-request: !2366
| * | CTest: Fix regression in ctest_start()Kyle Edwards2018-09-104-3/+14
| |/ | | | | | | | | | | | | | | The format for the TAG file was changed in 3.12, and the way it was read caused a regression which changed how the track was decided. This commit fixes the regression. Fixes #18347.
* | Merge branch 'ctest-fix-test-load' into release-3.12Brad King2018-09-1016-38/+74
|\ \ | |/ |/| | | Merge-request: !2362
| * CTest: Fix --test-load regressionBrad King2018-09-1016-38/+74
|/ | | | | | | | | | | | | | | | | | | | | | | The `ctest --test-load` option is implemented in `StartNextTests` by not starting any tests when the load is too high and instead sleeping and then returning. Prior to commit v3.11.0-rc1~117^2 (CTest: Re-implement test process handling using libuv, 2017-12-10) our outer loop in `RunTests` would immediately call `StartNextTests` again. However, now the `uv_run` loop may simply terminate if there are no tests running because no events are left pending. Fix this by converting the sleep in `StartNextTests` into a libuv timer that it starts instead. This avoids leaving `uv_run` with no pending events. In the case that there are other running tests this also allows CTest to detect when they finish even if it during the wait period where we previously slept. This regression was not caught by the test suite because it only verified that we do not start new tests when the load was too high and not that we proceed to start tests when the load drops. Revise the test suite to cover both. Fixes: #18338
* CMake 3.12.2v3.12.2Brad King2018-09-071-1/+1
|
* Merge branch 'FindMatlab-no-CMAKE_CL_64' into release-3.12Brad King2018-09-051-15/+0
|\ | | | | | | Merge-request: !2354
| * FindMatlab: Remove erroneous duplicate codeRaffi Enficiaud2018-09-051-15/+0
| | | | | | | | | | | | | | This was left accidentally when resolving merge conflicts between previous changes. Fixes: #18221
* | Merge branch 'vs-CMakeLists.txt' into release-3.12Brad King2018-09-051-1/+5
|\ \ | | | | | | | | | Merge-request: !2349
| * | VS: Restore CMakeLists.txt references in each targetBrad King2018-09-051-1/+5
| |/ | | | | | | | | | | | | | | | | | | | | | | | | The custom command de-duplication added by commit v3.12.0-rc1~171^2 (VS: Generate a custom command only in the least dependent target, 2018-03-23) accidentally also applied to the `CMakeLists.txt` file reference we put in each target. This file reference comes with a custom command that has no dependencies and that is safe to run repeatedly across multiple targets (via internal stamp checking). Therefore it should be excluded from the de-duplication so that `CMakeLists.txt` references appear in all targets for human reference. Fixes: #18310
* | Merge branch 'FindBoost-old-context' into release-3.12Brad King2018-09-041-1/+5
|\ \ | | | | | | | | | Merge-request: !2348
| * | FindBoost: Fix context discovery for 1.60 and belowIgor Kostenko2018-09-041-1/+5
| |/ | | | | | | | | | | | | | | | | * `all.hpp` was removed in 1.68: https://github.com/boostorg/context/commit/2e37599461912cc1679f106a25456a493f7f0b27 * `fcontext.hpp` was moved to detail in 1.61: https://github.com/boostorg/context/commit/c2f0dfdf2608c1ebaa2229fa6f358fe6aa103561 Fixes: #18126
* | Merge branch 'CheckIPOSupported-output-backslashes' into release-3.12Brad King2018-08-301-4/+11
|\ \ | | | | | | | | | Merge-request: !2331
| * | CheckIPOSupported: Tolerate backslashes in output of failed checksBrad King2018-08-301-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Avoid passing the output of our `try_compile` through a macro argument. Macro invocations re-parse their arguments and so should not be given arbitrary content that may contain backslashes and such. Instead pass a simple message. This is also more readable in the case that the macro generates a message itself. After the macro returns, report the real output directly to the variable named by our caller. Also record the output in a log file as other checks do on failure. Fixes: #18244
| * | CheckIPOSupported: Simplify result reporting logicBrad King2018-08-301-3/+4
| |/ | | | | | | | | | | Simplify the test for whether a `RESULT` argument was given to the `check_ipo_supported` call. Also do not set an empty variable name if `OUTPUT` was not given.
* | Merge branch 'android-ndk-r18' into release-3.12Brad King2018-08-285-9/+29
|\ \ | | | | | | | | | Merge-request: !2319
| * | Android: Add support for NDK r18Brad King2018-08-285-9/+29
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | NDK r18 drops GCC toolchains and some STL types. We need to choose a clang toolchain by default when no gcc toolchains are available. Switch the STL type default to `c++_static` when the old `gnustl_static` default is not available. Update the test suite to not run tests for STL types that do not exist. Also do not expect the gcc toolchain `cpp` tool to be available because r18 does not provide it. Also teach it to tolerate `gcc -dumpmachine` output like `arm--linux-android` that differs from the toolchain prefix. Fixes: #18301
* | Merge branch 'doc-clang-tidy-typo' into release-3.12Brad King2018-08-241-1/+1
|\ \ | | | | | | | | | Merge-request: !2303
| * | Help: Fix typo in clang-tidy example -checks optionDavid Demelier2018-08-241-1/+1
| |/
* | Merge branch 'FindCUDA-deprecate-cublas_device' into release-3.12Brad King2018-08-231-1/+2
|\ \ | | | | | | | | | Merge-request: !2298
| * | FindCUDA: Do not find cublas_device on CUDA >= 9.2Kenta Kubo2018-08-231-1/+2
| |/ | | | | | | | | | | | | The `cublas_device` has been deprecated and will be removed in future versions of CUDA. Issue: #18290
* | Merge branch 'cuda-no-cublas_device' into release-3.12Brad King2018-08-233-2/+8
|\ \ | | | | | | | | | Merge-request: !2296
| * | CUDA: Avoid using deprecated cublas_device to identify device lib dirsRobert Maynard2018-08-233-2/+8
| |/ | | | | | | | | | | | | Use `curand_static` to identify directories containing device libraries because `cublas_device` is deprecated and will be removed in the future. Issue: #18290
* | Merge branch 'state-reset-glob' into release-3.12Brad King2018-08-233-0/+11
|\ \ | | | | | | | | | Merge-request: !2278
| * | cmState: Clear GlobVerificationManager state on ResetShane Parris2018-08-093-0/+11
| |/ | | | | | | | | | | It should not persist across multiple configure rounds. Fixes: #18208
* | Merge branch 'export-properties-undefined' into release-3.12Craig Scott2018-08-183-0/+17
|\ \ | |/ |/| | | Merge-request: !2294
| * EXPORT_PROPERTIES: Prevent null dereference for undefined propertyCraig Scott2018-08-161-0/+5
| | | | | | Fixes: #18260
| * EXPORT_PROPERTIES: Add test for an undefined propertyCraig Scott2018-08-162-0/+12
|/ | | | The added test verifies that a property listed in EXPORT_PROPERTIES can be undefined. It confirms the crash recorded in issue #18260.
* CMake 3.12.1v3.12.1Brad King2018-08-091-1/+1
|
* Merge branch 'cuda-arch-version' into release-3.12Brad King2018-08-011-2/+3
|\ | | | | | | Merge-request: !2251
| * FindCUDA/select_compute_arch: Restore two-component CUDA_VERSIONBrad King2018-08-011-2/+3
| | | | | | | | | | | | | | | | | | | | Since commit v3.12.0-rc1~332^2 (FindCUDA/select_compute_arch: Add support for CUDA as a language, 2018-03-15) this module sets `CUDA_VERSION` based on `CMAKE_CUDA_COMPILER_VERSION` when the language is enabled. Limit it to two components for consistency with the normal `FindCUDA` documentation and behavior. Fixes: #18231
* | Merge branch 'UseSWIG-legacy-user-flags' into release-3.12Brad King2018-07-311-3/+4
|\ \ | | | | | | | | | Merge-request: !2245
| * | UseSWIG: restore legacy behavior for SWIG_MODULE_<name>_EXTRA_FLAGSMarc Chevrier2018-07-311-3/+4
|/ / | | | | | | Fixes: #18226
* | Merge branch 'cpack-default-package-version-zero' into release-3.12Craig Scott2018-07-298-12/+39
|\ \ | | | | | | | | | Merge-request: !2239
| * | CPack: Restore support for 0-valued version componentsBrad King2018-07-278-12/+39
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | In commit v3.12.0-rc1~136^2 (CPack: Use project version as default for `CPACK_PACKAGE_VERSION`, 2018-04-29) we did not account for the value of `CMAKE_PROJECT_VERSION_{MAJOR,MINOR,PATCH}` having `0`. Fix the logic to distinguish between unprovided version components and `0` components. While at it, add a test case covering the behavior described in the documentation by the original commit. The number of version components in the package name should match those provided to the `project()` command `VERSION` option. Fixes: #18199
* | Merge branch 'googletest_policy_settings' into release-3.12Brad King2018-07-251-0/+7
|\ \ | | | | | | | | | Merge-request: !2237
| * | GoogleTest: Ensure policy settings allow use of IN_LISTCraig Scott2018-07-251-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | If policy settings at the time the GoogleTest module is included are such that CMP0057 is unset or set to OLD, the use of IN_LIST with if() will lead to an error. Therefore, explicitly specify the policy settings for the whole file to ensure the function implementations have access to the required CMake features. Fixes: #18198
* | | Merge branch 'project-injected-no-cmp0048' into release-3.12Craig Scott2018-07-256-2/+25
|\ \ \ | |/ / |/| |
generated by cgit v0.12 at 2025-09-09 09:00:43 (GMT)