- Oct 17, 2016
-
-
b59b6dd9 cmRulePlaceholderExpander: Port clients to direct-use bdddd423 cmRulePlaceholderExpander: Extract from cmLocalGenerator f796e1b6 cmLocalGenerator: Move memset to cxx file c75a9d66 cmLocalGenerator: Use strings instead of a Target in rule replacement 46ad0d21 cmLocalGenerator: Use a converter in rule replacement API 2628dec1 cmLocalGenerator: Store variable replacements as state 315b9a31 cmLocalGenerator: Merge loops which populate mapping d5feb5b3 cmLocalGenerator: Populate variable mapping for all replacements efba22e1 cmLocalGenerator: Extract compiler option replacement from loop b29425f7 cmLocalGenerator: Populate a container of mappings for replacements f009d8f5 cmLocalGenerator: Move compiler option handling to be more direct 6cd27a85 cmLocalGenerator: Move variable to where it can be used easily 8b0e4795 cmLocalGenerator: Use the language from the compiler container 88016e2e cmLocalGenerator: Introduce a container of compiler names be87cb0c cmLocalGenerator: Simplify loop with range algorithm 425cd167 cmLocalGenerator: Remove the launcher from RuleVariables
-
3b6f1587 Factor IDE folder name retrieval out into helper method
-
e8bafb6f OS X: Do not try to set deployment target when cross-compiling
-
c05d9b05 Help: Fix math(EXPR) documentation formatting
-
78b00f1d Help: Clarify `ctest_*` APPEND option behavior
-
Add a `cmGeneratorTarget::GetEffectiveFolderName` helper to abstract lookup of the `FOLDER` property in combination with checking for generator support of folders.
-
The change in commit v3.4.0-rc2~6^2 (Xcode: Adjust deployment target SDK version to host version, 2015-10-11) does not make sense when cross-compiling. Make it conditional to fix this regression in some cross-compiling cases. Closes: #16355
-
Kitware Robot authored
-
- Oct 16, 2016
-
-
Kitware Robot authored
-
- Oct 15, 2016
-
-
Stephen Kelly authored
Add a factory function to cmLocalGenerator so that variableMappings can be provided from it, and so that Ninja can always have a hard-coded TargetImpLib.
-
Stephen Kelly authored
Implement cmLocalGenerator::ExpandRuleVariables in terms of the new class for source compatibility and to reduce diff noise in this commit.
-
Stephen Kelly authored
-
Stephen Kelly authored
Don't rely on the cmGeneratorTarget type needlessly.
-
Stephen Kelly authored
The rule replacement API should not really be in cmLocalGenerator, but it was historically, and this coupled many other things together here too, such as output conversion. Make the output converter a parameter so that rule replacement can be removed from cmLocalGenerator.
-
Stephen Kelly authored
These do not change over the lifetime of the cmLocalGenerator.
-
Stephen Kelly authored
-
Stephen Kelly authored
This reduces the final replacement to a simple query in the map, which is much more readable than what was here before.
-
Stephen Kelly authored
There is no need to be in the loop. Being there just adds to complexity.
-
Stephen Kelly authored
The same variables are replaced/retrieved from cmMakefile again and again. Use a container so that they don't have to be retrieved repeatedly, and to simplify the nested loop.
-
Stephen Kelly authored
-
Stephen Kelly authored
-
Stephen Kelly authored
This is just to make follow-up diffs smaller.
-
Stephen Kelly authored
Use it to determine when a rule replacement should gain extra options.
-
Stephen Kelly authored
-
Stephen Kelly authored
This one is not like the others as it doesn't participate in substitutions. Keep ExpandRuleVariables doing only one thing and make callers responsible for inserting a launcher prefix, simplifying the code all-around. Remove now-obsolete InsertRuleLauncher method.
-
Kitware Robot authored
-
- Oct 14, 2016
-
-
Brad King authored
-
Brad King authored
Explicitly state that this marks the `.xml` to tell the dashboard server to append it to previously submitted results and that it does not cause results to be appended to the `.xml` file.
-
Brad King authored
-
Ben Boeckel authored
The /TC flag causes all source files to be processed as C source files. We know that there is only one, so this is safe.
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Brad King authored
Visual Studio provides toolchains that are themselves built for 32-bit or 64-bit host architectures. By default it uses the 32-bit tools, but it can be told to prefer the 64-bit tools on 64-bit hosts. Extend the `CMAKE_GENERATOR_TOOLSET` specification to provide a way to request use of the 64-bit host tools. Closes: #15622
-
39b08858 cmSystemTools: Flush output buffer for list_item_verbose
-
19ffc072 Sublime: Exclude build tree from source tree project only optionally
-
20278872 Ninja: Fix POST_BUILD commands on macOS Frameworks
-
9977899d Ninja: Fix RC language depfile generation with cmcldeps
-