- Jun 13, 2013
-
-
Kitware Robot authored
-
- Jun 12, 2013
-
-
Kitware Robot authored
-
- Jun 11, 2013
-
-
Kitware Robot authored
-
- Jun 10, 2013
-
-
Brad King authored
-
Kitware Robot authored
-
- Jun 09, 2013
-
-
Kitware Robot authored
-
- Jun 08, 2013
-
-
Kitware Robot authored
-
- Jun 07, 2013
-
-
Kitware Robot authored
-
- Jun 06, 2013
-
-
Kitware Robot authored
-
- Jun 05, 2013
-
-
5b222354 Genex: Fix the HEAD target used for evaluated expressions
-
Brad King authored
-
Brad King authored
-
Brad King authored
-
21a0beac Xcode: Fix framework search paths in STATIC library targets (#14191)
-
d26800bc get_filename_component: Test ABSOLUTE of .. after root component
-
b62d440e Docs: Clarify CMAKE_PARENT_LIST_FILE (#14194)
-
273ecab9 CLI: Suppress the unused warning if the key value pair is cached.
-
a984f325 Introduce add_compile_options command.
-
If the expression $<TARGET_PROPERTY:prop> appears in the content of a target property, the target that prop is read from is the 'head target' of the expression. In contexts such as evaluating the content of a target property during generation, such as INCLUDE_DIRECTORIES, the 'head target' is the one on which the initial request was made. If evaluating a generator expression which is not a target property content, the target must be explicitly specified. Such contexts include add_custom_command and file(GENERATE). The content might then look like $<TARGET_PROPERTY:tgt,prop> However, as there is no HeadTarget set, any generator expressions evaluated as part of reading prop from tgt which do not specify the tgt directly report an error. Modify the logic of the TARGET_PROPERTY generator expression so that in such contexts, the 'head target' is set to the appropriate target which was first encountered.
-
Kitware Robot authored
-
- Jun 04, 2013
-
-
Brad King authored
In commit 2bc22bda (Xcode: Add frameworks search paths from link dependeny closure, 2012-12-07) we made framework search paths from the link closure conditional on target type, skipping it on STATIC and OBJECT library targets that do not actually link. However, the framework search paths also influence the compile lines (-F options) so we need them for all target types. The Makefile generator already does this, as did the Xcode generator prior to the above-mentioned commit.
-
Brad King authored
Teach the RunCMake.get_filename_component test to verify that ".." does not remove the root filename component.
-
Brad King authored
-
Extract upstream KWSys using the following shell commands. $ git archive --prefix=upstream-kwsys/ d79a792e | tar x $ git shortlog --no-merges --abbrev=8 --format='%h %s' dccf7725..d79a792e Brad King (1): d79a792e SystemTools: Fix CollapseFullPath to not erase root component Change-Id: I25c6600a621a960738b5afc0ba73f63df0693303
-
483e2084 OS X: Fix getting of CFBundle LOCATION property.
-
9ce60ff5 Qt4Macros: Allow specifying a TARGET in invokations of macros.
-
Brad King authored
Fix the wording of the documentation for CMAKE_PARENT_LIST_FILE to clarify that it only applies to the include stack in the current directory. Specify exactly what commands can include files instead of saying "somehow invoke".
-
Stephen Kelly authored
It is common to specify a CMAKE_TOOLCHAIN_FILE and get a warning for using it despite it not being used. The WarnUnusedCliUnused test relies on the warning being emitted each time cmake is run on an existing build. That behavior is changed by this patch to warn only on the first invokation of CMake, and not on subsequent invokations (because the variable is in the cache with the same value). For that test, a clean target is added which clears the cache and cause the warning to be emitted each time. As the Ninja generator does not support the feature needed to test this, it is not tested with that generator.
-
Stephen Kelly authored
-
Stephen Kelly authored
-
Stephen Kelly authored
This command is similar to add_definitions, in that it affects the compile options of all targets which follow it. The implementation is similar to the implementation of the include_directories command, in that it is based on populating a COMPILE_OPTIONS directory property and using that to initialize the same property on targets. Unlike the include_directories command however, the add_compile_options command does not affect previously defined targets. That is, in the following code, foo will not be compiled with -Wall, but bar will be: add_library(foo ...) add_compile_options(-Wall) add_library(bar ...)
-
Kitware Robot authored
-
- Jun 03, 2013