summaryrefslogtreecommitdiffstats
path: root/Source
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'vs_csharp_prop_for_all_extensions'Brad King2017-06-152-24/+49
|\ | | | | | | | | | | | | c90630c5 Vs: add support for VS_CSHARP_* target property for additional file extensions Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !961
| * Vs: add support for VS_CSHARP_* target property for additional file extensionsMichael Stürmer2017-06-132-24/+49
| | | | | | | | Fixes: #16726
* | Merge topic 'ipo-per-lang'Brad King2017-06-158-20/+28
|\ \ | | | | | | | | | | | | | | | | | | ba247cca IPO: Consider support for each language separately Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !964
| * | IPO: Consider support for each language separatelyBrad King2017-06-148-20/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | We only define `INTERPROCEDURAL_OPTIMIZATION` behavior for C, CXX, and Fortran languages. Do not try to enable support for other languages. Furthermore, each language builds with a different compiler, so check for support by CMake and the compiler for each language independently. Fixes: #16944
* | | Merge topic 'libuv-restore-fmode'Brad King2017-06-151-0/+16
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 871adefc cmake: Fix default file translate mode when using libuv Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !963
| * | | cmake: Fix default file translate mode when using libuvBrad King2017-06-141-0/+16
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On Windows, libuv's one-time initialization changes the C runtime library's `_fmode` setting to `_O_BINARY`, thus causing files to open as binary after that instead of the default `_O_TEXT` mode. See upstream libuv issue 840. Work around the problem by performing libuv initialization early and then restoring `_fmode`. In particular, this currently affects server mode. Without this fix, the `_fmode` setting changes when the server mode initializes libuv. Fixes: #16962
* | | CMake Nightly Date StampKitware Robot2017-06-151-1/+1
| | |
* | | Merge topic 'vs-dotnet-custom-reference-tags'Brad King2017-06-142-0/+32
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 07ec212a VS: add target property VS_DOTNET_REFERENCEPROP_<refname>_TAG_<tagname> Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !960
| * | | VS: add target property VS_DOTNET_REFERENCEPROP_<refname>_TAG_<tagname>Michael Stürmer2017-06-132-0/+32
| | |/ | |/| | | | | | | Fixes: #16689
* | | CMake Nightly Date StampKitware Robot2017-06-141-1/+1
| | |
* | | Merge topic 'remove-stray-line'Brad King2017-06-131-1/+0
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | ae77d976 cmGlobalGenerator: Remove unused line Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !955
| * | | cmGlobalGenerator: Remove unused lineBrad King2017-06-121-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove an unused line that was left by commit v2.4.0~3946 (set CMAKE_SYSTEM_VERSION for windows, 2003-07-16). Fixes: #16956
* | | | Merge topic 'cuda-dlink-no-deprecated-gpu'Brad King2017-06-131-0/+7
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | 7368ade2 CUDA: When linking device code suppress CUDA 8.0+ deprecation warnings Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !951
| * | | CUDA: When linking device code suppress CUDA 8.0+ deprecation warningsRobert Maynard2017-06-131-0/+7
| | |/ | |/| | | | | | | | | | | | | The CUDA compiler automatic deprecation warnings are pure noise when doing device linking, and should be suppressed to reduce the amount of confusion from users.
* | | CMake Nightly Date StampKitware Robot2017-06-131-1/+1
| | |
* | | Merge topic 'execute_process-pipeline-results'Brad King2017-06-121-1/+52
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | d6051ca3 execute_process: Add option to get results of every child Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !702
| * | | execute_process: Add option to get results of every childAdam Weisi2017-06-101-1/+52
| | | | | | | | | | | | | | | | | | | | Add a `RESULTS_VARIABLE` option to get the results of all children in a pipeline of one or more `COMMAND`s.
* | | | Merge topic 'cpack-freebsd-pkg'Brad King2017-06-124-0/+439
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2042cae9 CPack-FreeBSD: add a generator for FreeBSD pkg(8) Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !693
| * | | | CPack-FreeBSD: add a generator for FreeBSD pkg(8)Adriaan de Groot2017-06-104-0/+439
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds an option CPACK_ENABLE_FREEBSD_PKG to allow CPack to look for FreeBSD's libpkg / pkg(8). If this is set and the libpkg headers and library are found (which they will be, by default, on any FreeBSD system), then add a FreeBSD pkg(8) generator. The FreeBSD package tool pkg(8) uses tar.xz files (.txz) with two metadata files embedded (+MANIFEST and +COMPACT_MANIFEST). This introduces a bunch of FreeBSD-specific CPACK_FREEBSD_PACKAGE_* variables for filling in the metadata; the Debian generator does something similar. Documentation for the CPack CMake-script is styled after the Debian generator. Implementation notes: - Checks for libpkg -- the underlying implementation for pkg(8) -- and includes FreeBSD package-generation if building CMake on a UNIX host. Since libpkg can be used on BSDs, Linux and OSX, this potentially adds one more packaging format. In practice, this will only happen on FreeBSD and DragonflyBSD. - Copy-paste from cmCPackArchiveGenerator to special-case the metadata generation and to run around the internal archive generation: use libpkg instead. - Generating the metadata files is a little contrived. - Most of the validation logic for package settings is in CPackFreeBSD.cmake, as well as the code that tries to re-use packaging settings that may already be set up for Debian. - libpkg has its own notion of output filename, so we have another contrived bit of code that munges the output file list so that CPack can find the output. - Stick with C++98.
* | | | Merge topic 'cuda-compiler-launcher'Brad King2017-06-123-2/+5
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 414438b2 CUDA: Add option to run the compiler through launcher tools Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !949
| * | | | CUDA: Add option to run the compiler through launcher toolsBrad King2017-06-093-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a `CUDA_COMPILER_LAUNCHER` target property like those added for C and CXX by commit v3.4.0-rc1~450^2 (Add options to launch the compiler through tools like ccache or distcc, 2015-06-04). Fixes: #16953
* | | | | Merge topic 'update-kwsys'Brad King2017-06-122-15/+8
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3d1c3e0d Merge branch 'upstream-KWSys' into update-kwsys a3275878 KWSys 2017-06-09 (a700e2ab) Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !947
| * | | | | Merge branch 'upstream-KWSys' into update-kwsysBrad King2017-06-092-15/+8
| |/ / / / | | | | | | | | | | | | | | | | | | | | * upstream-KWSys: KWSys 2017-06-09 (a700e2ab)
* | | | | Merge topic 'file-generate-relative-paths'Brad King2017-06-124-3/+78
|\ \ \ \ \ | |_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 82be694c file(GENERATE): Add policy CMP0070 to define relative path behavior 69050f4d Tests: Use full output paths in file(GENERATE) calls Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !943
| * | | | file(GENERATE): Add policy CMP0070 to define relative path behaviorBrad King2017-06-094-3/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously `file(GENERATE)` did not define any behavior for relative paths given to the `OUTPUT` or `INPUT` arguments. Define behavior consistent with CMake conventions and add a policy to provide compatibility for projects that relied on the old accidental behavior. Fixes: #16786
* | | | | CMake Nightly Date StampKitware Robot2017-06-121-1/+1
| | | | |
* | | | | CMake Nightly Date StampKitware Robot2017-06-111-1/+1
| | | | |
* | | | | CMake Nightly Date StampKitware Robot2017-06-101-1/+1
| |/ / / |/| | |
* | | | Merge topic 'file-generate-path-cleanup'Brad King2017-06-091-5/+13
|\ \ \ \ | |/ / / | | | | | | | | | | | | | | | | | | | | c41a7c7d file: Normalize GENERATE command input and output file paths Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !940
| * | | file: Normalize GENERATE command input and output file pathsBrad King2017-06-081-5/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Normalize absolute paths so that no extra components like `../` or `...//...` appear that later confuse relative path computation. In particular, we expect paths sent to AddCMakeDependFile and AddCMakeOutputFile to be normalized. Do this only for paths that are already absolute because we can't handle relative paths yet (see #16786). Fixes: #16892
* | | | Merge topic 'qt-pass-point-by-value'Brad King2017-06-092-2/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 994beddb CMakeSetupDialog: Pass QPoint by value Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !946
| * | | | CMakeSetupDialog: Pass QPoint by valueDaniel Pfeifer2017-06-082-2/+2
| |/ / /
* | | | Merge topic 'no-return-void-expression'Brad King2017-06-092-2/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5b02bcf6 QtDialog/FirstConfigure: remove 'return' from void expression 2d1c05c1 cmGlobalGenerator: remove 'return' from void expression Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !941
| * | | | QtDialog/FirstConfigure: remove 'return' from void expressionDaniel Pfeifer2017-06-081-1/+1
| | | | |
| * | | | cmGlobalGenerator: remove 'return' from void expressionDaniel Pfeifer2017-06-081-1/+1
| |/ / /
* | | | Merge topic 'cpack-destructor-overrides'Brad King2017-06-098-8/+8
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 62eec34c Add CM_OVERRIDE to CPack generator destructors Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !939
| * | | | Add CM_OVERRIDE to CPack generator destructorsBrad King2017-06-088-8/+8
| |/ / /
* | | | Merge topic 'improve-msvc-feature-checks'Brad King2017-06-091-1/+3
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | f44d9bcc C++ feature checks: Improve exclusion of "0 Warning(s)" Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !938
| * | | | C++ feature checks: Improve exclusion of "0 Warning(s)"Brad King2017-06-081-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Simply matching "0 Warning" may match "10 Warning(s)". Instead remove the entire ` 0 Warning(s)` content from the MSBuild output before searching it for warnings. Issue: #16942
* | | | | CMake Nightly Date StampKitware Robot2017-06-091-1/+1
| |/ / / |/| | |
* | | | CMake Nightly Date StampKitware Robot2017-06-081-1/+1
| | | |
* | | | Merge topic 'autogen-no-vs-per-config'Brad King2017-06-071-0/+4
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | cc1b513d Autogen: Do not use per-config file suffixes with VS yet Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !932
| * | | | Autogen: Do not use per-config file suffixes with VS yetBrad King2017-06-071-0/+4
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The change in commit v3.9.0-rc1~42^2~1 (Autogen: Per-config file suffixes, 2017-05-15) broke Visual Studio builds because the generators do not yet fully support per-config sources. Disable the behavior on Visual Studio generators for now. Fixes: #16939
* | | | Merge topic 'fix-vs2017-featuredetect'Brad King2017-06-071-1/+1
|\ \ \ \ | | |/ / | |/| | | | | | | | | | | | | | | | | | f4ce3962 C++ feature checks: Do not match "0 Warning(s)" as a warning Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !930
| * | | C++ feature checks: Do not match "0 Warning(s)" as a warningWalter Gray2017-06-061-1/+1
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | The change in commit v3.9.0-rc1~6^2~1 (C++ feature checks: check output for '[Ww]arning', 2017-06-03) accidentally matches `0 Warning(s)` in the output and always thinks a warning exists, thus failing all checks in Visual Studio builds. Fixes: #16942
* | | Merge topic 'cmake_host_system_information-extend'Brad King2017-06-071-0/+49
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | e7869e80 cmake_host_system_information: Add more keywords Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !912
| * | | cmake_host_system_information: Add more keywordsFlorian Maushart2017-06-051-0/+49
| | |/ | |/| | | | | | | | | | Extend the `cmake_host_system_information()` command to add processor identification keywords.
* | | CMake Nightly Date StampKitware Robot2017-06-071-1/+1
| | |
* | | CMake Nightly Date StampKitware Robot2017-06-061-1/+1
|/ /
* | Begin post-3.9 developmentBrad King2017-06-051-2/+2
| |
generated by cgit v0.12 at 2025-02-12 10:04:51 (GMT)