- 12 Feb, 2018 1 commit
-
-
Kitware Robot authored
-
- 11 Feb, 2018 1 commit
-
-
Kitware Robot authored
-
- 10 Feb, 2018 1 commit
-
-
Kitware Robot authored
-
- 09 Feb, 2018 1 commit
-
-
Kitware Robot authored
-
- 08 Feb, 2018 1 commit
-
-
Kitware Robot authored
-
- 07 Feb, 2018 1 commit
-
-
Kitware Robot authored
-
- 06 Feb, 2018 1 commit
-
-
Kitware Robot authored
-
- 05 Feb, 2018 3 commits
-
-
Brad King authored
-
Brad King authored
-
Kitware Robot authored
-
- 04 Feb, 2018 1 commit
-
-
Kitware Robot authored
-
- 03 Feb, 2018 1 commit
-
-
Kitware Robot authored
-
- 02 Feb, 2018 2 commits
-
-
Sebastian Holtermann authored
For multi configuration generators AUTOMOC generates the moc files that are included in `mocs_compilation.cpp` in `AUTOGEN_BUILD_DIR/include_$<CONFIG>/`. By doing so each configuration reads different moc files when compiling `mocs_compilation.cpp`. Since we do not (need to) rewrite `mocs_compilation.cpp` on a configuration change anymore, the files also does not need to be recompiled anymore. Not having to rewrite and recompile `mocs_compilation.cpp` on a configuration change anymore was the main objective of this patch. In a similar fashion AUTORCC generates a `qrc_BASE_CMAKE.cpp` file below `AUTOGEN_BUILD_DIR/include_$<CONFIG>/` and `qrc_BASE.cpp` becomes a mere wrapper that includes this actuall rcc output file (when using multi configuration generators). The template files `Modules/AutoRccInfo.cmake.in` and `Modules/AutogenInfo.cmake.in` were removed in favor of writing the info `.cmake` files manually. Closes #17230
-
Kitware Robot authored
-
- 01 Feb, 2018 4 commits
-
-
Vitaly Stakhovsky authored
It is no longer used outside this class, so its scope can be limited to file.
-
Brad King authored
In commit v3.4.0-rc1~480^2~3 (cmCustomCommandGenerator: Port to cmOutputConverter, 2015-06-04), cmCustomCommandGenerator's access to the local generator was removed so it needed to construct its own cmOutputConverter instance. Access to the local generator was then restored by commit v3.4.0-rc1~285^2~21 (cmCustomCommandGenerator: Require cmLocalGenerator in API, 2015-07-25), so now we can use its cmOutputConverter base class methods directly.
-
Brad King authored
Remove the `PRE_LINK` and `POST_BUILD` variables. They are not referenced by `WriteDeviceLinkRule`. Remove the `byproducts` local variable from `WriteDeviceLinkStatement` and all the code populating it. We never used the result.
-
Kitware Robot authored
-
- 31 Jan, 2018 9 commits
-
-
Static string comparisons were causing heap allocations just for a comparison.
-
-
In standard libraries, `std::string::find` is usually implemented using vectorized code. Since the Tokenize method iterates character-by-character, doing an initial check using `find` improves performance.
-
Similar to 66076915, the `SetProperty` side is showing up in performance listings due to string comparisons.
-
-
-
Callgrind indicated that `strlen` was being called a lot of times here due to the string comparisons. Since keywords are "sparse" in `add_custom_command`, use a hash comparison to handle keywords and then use strings for comparison since they have a built-in length parameter.
-
Pavel Solodovnikov authored
* Change some functions to take `std::string` instead of `const char*` in the following classes: `cmMakeFile`, `cmake`, `cmCoreTryCompile`, `cmSystemTools`, `cmState`, `cmLocalGenerator` and a few others. * Greatly reduce using of `const char*` overloads for `cmSystemTools::MakeDirectory` and `cmSystemTools::RelativePath`. * Remove many redundant `c_str()` conversions throughout the code.
-
Kitware Robot authored
-
- 30 Jan, 2018 7 commits
-
-
For large number of targets significant amount of time is spent in cmLocalGenerator::FindGeneratorTargetToUse, which uses find_if on a vector to locate the given target. Using a map instead of vector for ImportedGeneratorTargets (as done for cmMakefile::ImportedTargets) provides a significant speedup (up to factor of 2).
-
Frank Winklmeier authored
GetImportedGeneratorTargets is not used anywhere hence remove it to avoid exposing the type of ImportedGeneratorTargets.
-
Robert Maynard authored
The default that CUDA uses causes failures when you try to embed CUDA obj's into another target.
-
Move the `AdditionalIncludeDirectories` tag back to the VS-preferred location in `.vcxproj` files. Fixes: #17691
-
Kitware Robot authored
-
- 29 Jan, 2018 3 commits
-
-
Brad King authored
Move the method implementation up to `cmLocalCommonGenerator` to avoid duplicating it in each generator.
-
Brad King authored
Clang incorrectly warns about a case where we initialize a variable inside a condition in such a way that it will always be initialized before we use it. Simply initialize the variable when defining it to silence the warning.
-
Kitware Robot authored
-
- 28 Jan, 2018 1 commit
-
-
Kitware Robot authored
-
- 27 Jan, 2018 1 commit
-
-
Kitware Robot authored
-
- 26 Jan, 2018 1 commit
-
-
Robert Dailey authored
Previously, code wrote out empty tags for `<DebugInformationFormat>` like so: <DebugInformationFormat></DebugInformationFormat> This gets corrected by Visual Studio 2017 when saving the solution. The correction appears as: <DebugInformationFormat> </DebugInformationFormat> In the spirit of keeping the XML structure as close to what Visual Studio expects as possible, a newline is inserted after the opening tag in the empty case.
-