summaryrefslogtreecommitdiffstats
path: root/Source
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'thread-sanitizer'Brad King2014-07-094-155/+337
|\ | | | | | | | | | | 7c80ce6f Help: Add notes for topic 'thread-sanitizer' 49948f72 ctest_memcheck: Add support for ThreadSanitizer
| * ctest_memcheck: Add support for ThreadSanitizerBill Hoffman2014-07-094-155/+337
| | | | | | | | | | | | | | | | | | This commit adds support for ThreadSanitizer to ctest. ThreadSanitizer is part of the clang compiler and also gcc 4.8 and later. You have to compile the code with special flags. Then your code gets the the ThreadSanitizer ability built into it. To pass options to the ThreadSanitizer you use an environment variable. This commit teaches ctest to parse the output from ThreadSanitizer and send it to CDash.
* | Merge topic 'dev/custom-target-performance'Brad King2014-07-093-44/+62
|\ \ | | | | | | | | | | | | | | | | | | 6208c285 cmMakefile: Defer dependency calculations dc2e26df cmMakefile: Avoid excess source files d2803fba cmMakefile: Add a CreateSource method
| * | cmMakefile: Defer dependency calculationsBen Boeckel2014-07-081-7/+7
| | |
| * | cmMakefile: Avoid excess source filesBen Boeckel2014-07-081-23/+26
| | | | | | | | | | | | | | | When there are no commands, a main_dependency is not required and when there are also no dependencies, nothing is required.
| * | cmMakefile: Add a CreateSource methodBen Boeckel2014-07-083-14/+29
| | | | | | | | | | | | | | | The GetOrCreateSource searches the source file listing again, but some callers know that it already didn't exist.
* | | Merge topic 'allow-OBJECT-library-extra-sources'Brad King2014-07-091-5/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 2c470b77 add_library: Allow arbitrary non-linked sources in OBJECT libraries de4f3e2c Tests: Fix broken dependency in ObjectLibrary test 54bf5858 Tests: Resolve TODO comment left in ObjectLibrary test
| * | | add_library: Allow arbitrary non-linked sources in OBJECT librariesBrad King2014-07-091-5/+2
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | Loosen this restriction on OBJECT libraries to allow source files of any name to be generated by custom commands or listed for reference in IDE projects so long as they would not affect linking of a normal library. Update the rejection message to be more specific about the looser restriction. Extend the ObjectLibrary test to cover a ".cmake" file generated by a custom command in an OBJECT library.
* | | Merge topic 'update-kwsys'Brad King2014-07-097-74/+432
|\ \ \ | | | | | | | | | | | | | | | | | | | | 5f525da0 Merge branch 'upstream-kwsys' into update-kwsys 3d127627 KWSys 2014-07-02 (c2a329ce)
| * | | Merge branch 'upstream-kwsys' into update-kwsysBrad King2014-07-077-74/+432
| |/ /
* | | CMake Nightly Date StampKitware Robot2014-07-091-1/+1
| |/ |/|
* | CMake Nightly Date StampKitware Robot2014-07-081-1/+1
|/
* Merge topic 'refactor-usage-requirement-evaluation'Brad King2014-07-077-261/+113
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 93790506 cmTarget: Simplify INTERFACE_INCLUDE_DIRECTORIES usage requirement lookup b5b098eb cmTarget: Simplify CMP0027 logic in processIncludeDirectories 5e07dcf7 cmTarget: Add to LinkImplementation whether each library was a genex f77b384c cmTarget: Simplify INTERFACE_COMPILE_FEATURES usage requirement lookup 61ef8daa cmTarget: Simplify INTERFACE_COMPILE_DEFINITIONS usage requirement lookup d9586f83 cmTarget: Simplify INTERFACE_COMPILE_OPTIONS usage requirement lookup 3156275b cmTarget: Simplify INTERFACE_SOURCES usage requirement lookup 363cd33e cmTarget: Add method to add usage requirements from linked interfaces 251e835b cmTarget: Add to LinkImplementation a backtrace for each library 848c8ccf cmTarget: Refactor LinkImplementation to allow more information f85ccf23 cmGeneratorExpressionEvaluator: Shorten some long lines 82e91e34 cmComputeLinkDepends: Convert AddLinkEntries to a template
| * cmTarget: Simplify INTERFACE_INCLUDE_DIRECTORIES usage requirement lookupBrad King2014-07-071-61/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | Use the AddInterfaceEntries helper to avoid duplication. In TargetPropertyEntry, replace the TargetName string member with a reference to the full cmLinkImplItem that produced the entry. This is possible because the cmLinkImplItem is available in AddInterfaceEntries (it was not available in GetIncludeDirectories). Having the full cmLinkImplItem allows processIncludeDirectories to implement CMP0027 OLD behavior without repeating the target name lookup. Update the RunCMake.CompatibleInterface test DebugProperties case expected output for the new order of the messages.
| * cmTarget: Simplify CMP0027 logic in processIncludeDirectoriesBrad King2014-07-071-26/+20
| | | | | | | | | | | | | | | | | | Evaluate and lookup the target name only once per TargetPropertyEntry instead of repeating it for each include directory entry. Use a local checkCMP0027 variable to record whether the policy should be checked. Evaluate the target name as a generator expression only if it looks like one. Lookup the target by name only after evaluation of generator expressions.
| * cmTarget: Add to LinkImplementation whether each library was a genexBrad King2014-07-072-11/+11
| | | | | | | | | | | | Implementation of CMP0027 OLD behavior needs to know whether each entry in LinkImplementation::Libraries came from a generator expression or not. Add a FromGenex member to cmLinkImplItem to record this.
| * cmTarget: Simplify INTERFACE_COMPILE_FEATURES usage requirement lookupBrad King2014-07-071-39/+3
| | | | | | | | Use the AddInterfaceEntries helper to avoid duplication.
| * cmTarget: Simplify INTERFACE_COMPILE_DEFINITIONS usage requirement lookupBrad King2014-07-071-39/+3
| | | | | | | | Use the AddInterfaceEntries helper to avoid duplication.
| * cmTarget: Simplify INTERFACE_COMPILE_OPTIONS usage requirement lookupBrad King2014-07-071-39/+3
| | | | | | | | Use the AddInterfaceEntries helper to avoid duplication.
| * cmTarget: Simplify INTERFACE_SOURCES usage requirement lookupBrad King2014-07-071-39/+3
| | | | | | | | Use the AddInterfaceEntries helper to avoid duplication.
| * cmTarget: Add method to add usage requirements from linked interfacesBrad King2014-07-071-0/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Create a cmTargetInternals::AddInterfaceEntries method to construct a $<TARGET_PROPERTY:tgt,INTERFACE_XYZ> generator expression and evaluate it for every target in the link implementation. This will be useful to de-duplicate such evaluation for each usage requirement separately. The new method will soon be used in the implementation of the INTERFACE_* usage requirement lookup methods (GetSourceFiles, GetCompileOptions, GetCompileDefinitions, GetCompileFeatures, GetIncludeDirectories). It is necessary for these methods to determine whether an expression in LinkImplementationPropertyEntries evaluates to a target or not because generator expression evaluation reports an error for non-targets and we construct a $<TARGET_PROPERTY:tgt,INTERFACE_XYZ> expression for each entry that is a target. The implementation of each usage requirement currently processes the LinkImplementationPropertyEntries and evaluates all generator expressions to determine targets. That is no longer necessary because GetLinkImplementationLibraries now returns resolved and cached targets together with their name. Use it to implement AddInterfaceEntries.
| * cmTarget: Add to LinkImplementation a backtrace for each libraryBrad King2014-07-072-5/+7
| | | | | | | | Allow clients to provide backtrace context on evaluation diagnostics.
| * cmTarget: Refactor LinkImplementation to allow more informationBrad King2014-07-075-14/+27
| | | | | | | | | | | | | | Create a cmLinkImplItem class derived from cmLinkItem so more information can be added to link implementation entries than link interface entries. Convert the LinkImplementation Libraries member to hold it. Update client sites accordingly.
| * cmGeneratorExpressionEvaluator: Shorten some long linesBrad King2014-07-071-13/+16
| | | | | | | | Adjust the definitions of getLinkedTargetsContent to avoid long lines.
| * cmComputeLinkDepends: Convert AddLinkEntries to a templateBrad King2014-07-072-4/+5
| | | | | | | | | | Allow the method to be called with a vector of any type that can be converted to cmLinkItem.
* | Merge topic 'ctest-S-message-STATUS'Brad King2014-07-071-0/+11
|\ \ | | | | | | | | | | | | f33d875a CTest: Implement message(STATUS) output for 'ctest -S' scripts
| * | CTest: Implement message(STATUS) output for 'ctest -S' scriptsBrad King2014-07-021-0/+11
| |/ | | | | | | | | | | Send status messages to the CTest HANDLER_OUTPUT log since they are part of the script handler output. This also ensures they appear inline with other test command handler output.
* | CMake Nightly Date StampKitware Robot2014-07-071-1/+1
| |
* | CMake Nightly Date StampKitware Robot2014-07-061-1/+1
| |
* | CMake Nightly Date StampKitware Robot2014-07-051-1/+1
| |
* | CMake Nightly Date StampKitware Robot2014-07-041-1/+1
| |
* | CMake Nightly Date StampKitware Robot2014-07-031-1/+1
|/
* Merge topic 'fix-circular-transitive-properties-segfault'Brad King2014-07-022-0/+43
|\ | | | | | | | | | | 65aa5442 Target: Return null when a transitive property is not defined. 61ce6547 Genex: Fix stack overflow in transitive property evaluation.
| * Target: Return null when a transitive property is not defined.Stephen Kelly2014-07-011-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit v2.8.11~310^2~1 (Keep track of INCLUDE_DIRECTORIES as a vector of structs., 2012-11-19) added special case of INCLUDE_DIRECTORIES for the purpose of origin-tracking of individual entries in the property. It introduced a bug in that it returned an empty string instead of '0' in the case that no includes have been set. Commit v2.8.11~289^2~2 (Handle INTERFACE properties transitively for includes and defines., 2012-09-23) introduced transitive handling of the property through the link implementation, together with a whitelist of properties which would be evaluated transitively. Because of the bug introduced previously, the 'prop' in TargetPropertyNode is non-null, meaning that the content (the empty string) would be evaluated as a generator expression. This was harmless as the follow-up code was only for 'INTERFACE_' variants of target properties, so the effect was the same. Commits v2.8.11~280^2~2 (Keep track of properties used to determine linker libraries., 2012-11-05) and v2.8.11~280^2~1 (Add API to calculate link-interface-dependent bool properties or error., 2013-01-06) added a way to track and report errors on properties which both determine and are determined by the link implementation. This was later used in generator expression evaluation by commit v2.8.11~252^2~2 (Make INTERFACE determined properties readable in generator expressions., 2013-01-19). If a property is unset (null), and the link implementation of the target was not being evaluated, this commit made it possible to evaluate the property from the link implementation instead. If the link implementation was being evaluated, an empty string was returned from the generator expression evaluation, which might be later reported as an error. The above logic was written for 'compatible interface' properties, but in fact it should have also included other properties. Because of the empty-string-instead-of-null bug, this code block is not entered for the INCLUDE_DIRECTORIES property. At this point, however, the bug still does not significantly affect behavior, because the follow-up code is still a no-op for the INCLUDE_DIRECTORIES property, and an empty string is returned regardless. Commit v2.8.11~189^2~6 (Use the link information as a source of compile definitions and includes., 2013-02-12) refactored the logic, but also without a change in behavior. Commit v2.8.11~156^2~2 (Expand includes and defines transitively in 'external' genexes., 2013-02-13) refactored the logic again, this time with a change of behavior. The INCLUDE_DIRECTORIES property was then mapped to INTERFACE_INCLUDE_DIRECTORIES during transitive generator expression evaluation. Because the transitive evaluation involved evaluation of the link implementation, this introduced a recursive loop and a segfault with code like: add_library(empty1 ...) add_library(empty2 ...) target_link_libraries(empty1 PRIVATE $<$<STREQUAL:$<TARGET_PROPERTY:INCLUDE_DIRECTORIES>,/foo/bar>:empty2> ) As there is no real use-case for reading a target property like that while evaluating the link implementation, this went unnoticed. The same pattern was followed for other special-cased reads of transitive target properties such as COMPILE_DEFINITIONS. The segfault was fixed in the parent commit, but change the property to return null when appropriate for other future uses.
| * Genex: Fix stack overflow in transitive property evaluation.Stephen Kelly2014-07-011-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit v2.8.11~156^2~2 (Expand includes and defines transitively in 'external' genexes., 2013-02-13) introduced a recursive loop and a stack overflow during evaluation of a link implementation which depends on a transitive property, such as add_library(empty1 ...) add_library(empty2 ...) target_link_libraries(empty1 PRIVATE $<$<STREQUAL:$<TARGET_PROPERTY:INCLUDE_DIRECTORIES>,/foo/bar>:empty2> ) There is no use-case for code like that currently, but it should not cause a stack overflow. Avoid the recursion by reporting an error early if a case like this is found.
* | Merge topic 'ninja-link-order-only-dependencies'Brad King2014-07-021-1/+6
|\ \ | | | | | | | | | | | | ac8879ce Ninja: Add order-only dependencies to link commands (#14728)
| * | Ninja: Add order-only dependencies to link commands (#14728)Ben Boeckel2014-07-011-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A library or executable target that consists only of a reference to an object library may have no sources to compile or custom commands to run. The command in the target is the link (or archive) command. Add missing order-only dependencies to link commands so that target ordering dependencies are satisfied for it without depending on an intermediate compilation rule. Extend the ObjectLibrary test to cover this case. Co-Author: Brad King <brad.king@kitware.com>
* | | Merge topic 'encoding-bugs'Brad King2014-07-022-15/+5
|\ \ \ | | | | | | | | | | | | | | | | 9571214e Encoding: Replace some system calls with kwsys calls which handle unicode.
| * | | Encoding: Replace some system calls with kwsys calls which handle unicode.Clinton Stimpson2014-07-012-15/+5
| | | |
* | | | Merge topic 'libarchive-encoding'Brad King2014-07-022-8/+56
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | 71c981a2 Encoding: Fix potential encoding issues with libarchive on Windows.
| * | | | Encoding: Fix potential encoding issues with libarchive on Windows.Clinton Stimpson2014-07-022-8/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Because the 8bit string encoding in libarchive can be different than the 8bit string encoding in CMake, change to call the wide version of libarchive functions. They are different if CMake is configured to use UTF-8 as the internal encoding. Create helper functions for some libarchive calls to use wstring internally on platforms supporting it.
* | | | | CMake Nightly Date StampKitware Robot2014-07-021-1/+1
| |_|/ / |/| | |
* | | | Merge topic 'ninja-no-phony-sources'Brad King2014-07-014-44/+44
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | 93371ed5 Ninja: Skip generating empty phony rules 7243c951 Ninja: Don't limit custom cmd side-effects to build folder (#14972) a33cf6d0 Ninja: Consider only custom commands deps as side-effects (#14972)
| * | | Ninja: Skip generating empty phony rulesAdam Strzelecki2014-06-302-14/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ninja generator ensures that all custom commands being target dependencies are run before other source compilations. However in case there are no such dependencies it currently generates empty phony rules which clutter the build graph. Teach the Ninja generator to produce such rules only when necessary.
| * | | Ninja: Don't limit custom cmd side-effects to build folder (#14972)Adam Strzelecki2014-06-301-16/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Actually custom command can write wherever it wants to, such as temporary folder or source folder, possibly violating rules that only build folder should be affected. Therefore we should consider custom command dependency at any path as possible side effect adding phony rule. We avoid adding phony rules for regular source files (since the paraent commit) so we no longer need the in-build-tree test to avoid them.
| * | | Ninja: Consider only custom commands deps as side-effects (#14972)Adam Strzelecki2014-06-302-14/+17
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit v2.8.12~248^2 (Ninja: Custom Command file depends don't need to exist before building, 2013-06-07) all explicit dependencies inside build folder were considered as possible build command side-effects and phony rules were produced for them in case they don't exist when starting to build. This is unnecessary since regular compile inputs need to exist or cmake will fail. Moreover the exception for sources having GENERATED property that can be missing is already handled by WriteAssumedSourceDependencies. This fixes unwanted phony rules for all regular source files when doing in-source build, causing Ninja not complain when such files gets missing, i.e. during development. Also this reduces number of rules in ninja.build. Now only custom command dependencies are considered as possible side-effects.
* | | CMake Nightly Date StampKitware Robot2014-07-011-1/+1
| | |
* | | Merge topic 'vs14-generator'Brad King2014-06-3011-4/+923
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | f0e298ad Help: Add notes for topic 'vs14-generator' 5c105140 Tests: Simplify LoadCommand tests b1cbd577 FindBoost: Add -vc140 mangling for VS 14 bdc7d9c8 VS14: Fix Cl and Link flag tables as previous versions d96b3f68 VS14: Generate flag tables from MSBuild v140 tool files 65624c39 VS14: Add Visual Studio 14 generator (#14982) 8635ac23 Tests/Preprocess: Remove unnecessary VS version tests
| * | | VS14: Fix Cl and Link flag tables as previous versionsBrad King2014-06-252-11/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Apply the flag table fixes from: commit 9c7f234c (VS: Fix /MANIFESTUAC:NO linker option mapping, 2014-05-07) commit e8633e66 (VS: Fix /analyze:log flag mapping, 2014-04-01) commit f2caf795 (VS: Fix /MAP:mapfile flag mapping, 2013-07-09) to the VS 14 flag tables.
| * | | VS14: Generate flag tables from MSBuild v140 tool filesBrad King2014-06-255-3/+759
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Run cmparseMSBuildXML.py on cl.xml, lib.xml, and link.xml to generate our flag tables: python cmparseMSBuildXML.py -x ".../MSBuild/Microsoft.Cpp/v4.0/V140/1033/cl.xml" > cmVS14CLFlagTable.h python cmparseMSBuildXML.py -x ".../MSBuild/Microsoft.Cpp/v4.0/V140/1033/lib.xml" > cmVS14LibFlagTable.h python cmparseMSBuildXML.py -x ".../MSBuild/Microsoft.Cpp/v4.0/V140/1033/link.xml" > cmVS14LinkFlagTable.h Fix up the declaration names at the top of each file. Finally, teach cmVisualStudio10TargetGenerator to select the version of the table matching the version of VS. Co-Author: Pawel Stopinski <diokhan@go2.pl>
generated by cgit v0.12 at 2025-02-07 10:52:39 (GMT)