- 27 Jul, 2016 3 commits
-
-
Daniel Pfeifer authored
Automate with: find Tests -type f -print0 | xargs -0 perl -i -0pe \ 's/set\(([a-zA-Z0-9_]+)(\s+)"\$\{\1\}([^"])/string(APPEND \1\2"\3/g'
-
Daniel Pfeifer authored
Automate with: find Modules -type f -print0 | xargs -0 perl -i -0pe \ 's/set\(([a-zA-Z0-9_]+)(\s+)"\$\{\1\}([^"])/string(APPEND \1\2"\3/g'
-
Kitware Robot authored
-
- 26 Jul, 2016 1 commit
-
-
Kitware Robot authored
-
- 25 Jul, 2016 1 commit
-
-
Kitware Robot authored
-
- 24 Jul, 2016 1 commit
-
-
Kitware Robot authored
-
- 23 Jul, 2016 1 commit
-
-
Kitware Robot authored
-
- 22 Jul, 2016 10 commits
-
-
Brad King authored
-
Brad King authored
-
Brad King authored
-
Kitware Robot authored
-
- 21 Jul, 2016 14 commits
-
-
Brad King authored
If `--help` is not a valid option then it may print content to stderr, so we need to capture that.
-
Benjamin Ballet authored
Otherwise `CMAKE_VS_PLATFORM_TOOLSET` is not set even though the `v100` toolset is chosen.
-
Brad King authored
Teach Visual Studio generators to include object files from object libraries in the list of objects whose symbols are to be exported. The Makefile and Ninja generators already did this. Update the test to cover this case. Reported-by:
Bertrand Bellenot <Bertrand.Bellenot@cern.ch>
-
Patrick Boettcher authored
This commit updates the vim-syntax-file. It is still not complete, but contains much more keywords, built-in variables. Generator expressions are highlighted as well. This file is generated from a script which parses the --help output of cmake 3.5. Imported from here: https://github.com/pboettch/vim-cmake-syntaxSigned-off-by:
Patrick Boettcher <patrick.boettcher@posteo.de>
-
Brad King authored
-
Brad King authored
-
Justin Clift authored
Protect our `$0` reference in the shell as `"$0"`. Otherwise it works with a space in the path only due to an insecure Windows feature. Prior to this fix, any installer using the option added by commit v2.8.9~234^2 (Added CPACK_NSIS_ENABLE_UNINSTALL_BEFORE_INSTALL, 2011-06-11) exposes a local privilege escalation vulnerability. Reported-by:
Amir Szekely <kichik@gmail.com> Reported-by: Ug_0 Security
-
Brad King authored
Revert these commits: * v3.6.0-rc1~134^2 Tests: QtAutogen: Same source name in different directories test, 2016-04-13 * v3.6.0-rc1~134^2~1 Autogen: Generate qrc_NAME.cpp files in subdirectories, 2016-04-19 * v3.6.0-rc1~134^2~2 Autogen: Generate not included moc files in subdirectories, 2016-04-19 They regress existing builds that depend on the paths/symbols generated previously. Another approach will be needed to solve the name collision problem they were intended to solve. Leave the error diagnostics for the colliding cases that were added in the same topic as the above commits because they provide a useful early failure in relevant cases. Fixes #16209.
-
Kitware Robot authored
-
- 20 Jul, 2016 9 commits
-
-
Brad King authored
Use response files for object file lists that approach the scale of the system `ARG_MAX` limit. Fixes #16206.
-
Brad King authored
Factor CMAKE_<LANG>_USE_RESPONSE_FILE_FOR_{OBJECTS,LIBRARIES} lookup out into a common helper. Use a separate helper for each because more specific logic may be added to each later.
-
Brad King authored
Custom command dependencies are followed for each target's source files and add their transitive closure to the corresponding target. This means that when a custom command in one target has a dependency on a custom command in another target, both will appear in the dependent target's sources. For the Makefile, VS IDE, and Xcode generators this is not a problem because each target gets its own independent build system that is evaluated in target dependency order. By the time the dependent target is built the custom command that belongs to one of its dependencies will already have been brought up to date. For the Ninja generator we need to generate a monolithic build system covering all targets so we can have only one copy of a custom command. This means that we need to reconcile the target-level ordering dependencies from its appearance in multiple targets to include only the least-dependent common set. This is done by computing the set intersection of the dependencies of all the targets containing a custom command. However, we previously included only the direct dependencies so any target-level dependency not directly added to all targets into which a custom command propagates was discarded. Fix this by computing the transitive closure of dependencies for each target and then intersecting those sets. That will get the common set of dependencies. Also add a test to cover a case in which the incorrectly dropped target ordering dependencies would fail.
-
Benjamin Ballet authored
Although we provide a `VS_GLOBAL_ROOTNAMESPACE` option to both set the `RootNamespace` value and reference it, some users may try to set `VS_GLOBAL_RootNamespace` to set `RootNamespace` as a variant of the `VS_GLOBAL_<variable>` property. In this case we still need to add the reference to `$(RootNamespace)`.
-
Brad King authored
Bootstrapping under MSYS2 is the same as under MSYS/MinGW except that `uname` reports `MSYS...` instead of `MINGW...`.
-
Dāvis Mosāns authored
-
Brad King authored
* upstream-KWSys: KWSys 2016-07-19 (9d1dbd95)
-
Kitware Robot authored
Code extracted from: http://public.kitware.com/KWSys.git at commit 9d1dbd95835638e4c0fcf74dc8020cd4cd3426c1 (master). Upstream Shortlog ----------------- Dāvis Mosāns (2): d2cdfc6d FStream: Use common base for basic_ifstream and basic_ofstream 9d1dbd95 FStream: Add MinGW support
-