summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Tests: Avoid CTestLimitDashJ crash on Borland 5.8 buildsBrad King2013-01-311-0/+1
| | | | | | | | | | | | The test added by commit e378ba5f (Add CTestLimitDashJ test, 2012-12-26) crashes with CTest compiled by Borland 5.8. There seems to be interaction among the large number of internal ctest runs. It is probably related to the undiscovered underlying issue mentioned in commit 32478069 (CTest: Prevent creation of unbounded number of tests in ctest, 2012-12-18) when fixing the symptom covered by the CTestLimitDashJ test. Add --force-new-ctest-process to avoid the crash. Further investigation will still be needed to identify the true problem.
* Merge topic 'fix-target-property-commands'Brad King2013-01-3012-83/+98
|\ | | | | | | | | | | | | 7bf490e Make subclasses responsible for joining content. f6b16d4 Don't allow targets args in the new target commands. b3a7e19 Make the Property name protected so that subclasses can use it.
| * Make subclasses responsible for joining content.Stephen Kelly2013-01-2911-18/+89
| | | | | | | | | | This way we can add handling of relative/absolute paths and of -D in compile definitions.
| * Don't allow targets args in the new target commands.Stephen Kelly2013-01-299-74/+16
| |
| * Make the Property name protected so that subclasses can use it.Stephen Kelly2013-01-291-1/+3
| | | | | | | | Makes subclasses more dry in upcoming patches.
* | CMake Nightly Date StampKitware Robot2013-01-301-1/+1
| |
* | Merge topic 'fix-TARGET_PROPERTY-extraction'Brad King2013-01-292-11/+5
|\ \ | | | | | | | | | | | | 5daaa5c Fix TARGET_PROPERTY target extractions.
| * | Fix TARGET_PROPERTY target extractions.Stephen Kelly2013-01-292-11/+5
| | | | | | | | | | | | | | | | | | | | | We need to make sure we can export targets which have content such as $<0:$<TARGET_PROPERTY:not_a_target,INTERFACE_INCLUDE_DIRECTORIES> That means making not finding a target non-fatal here.
* | | Merge topic 'FindGTK2-lib-order'Brad King2013-01-291-35/+41
|\ \ \ | | | | | | | | | | | | | | | | 399c3b8 FindGTK2: Fix GTK2_LIBRARIES order for static gtk libraries
| * | | FindGTK2: Fix GTK2_LIBRARIES order for static gtk librariesRodolfo Schulz de Lima2013-01-281-35/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before this, when creating GTK2_LIBRARIES, FindGTK2 added the GTK dependencies in wrong order into GTK2_LIBRARIES. With dynamic libraries this is not a major problem, but when linking to static gtk libraries, the linker outputs a lot of undefined symbols. Reorder the calls that append libraries to GTK2_LIBRARIES to respect dependency order.
* | | | Merge topic 'DocumentRelativePathHandling'Brad King2013-01-292-6/+5
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | a7d6ebb documentation: handling of relative paths by include- and link_directories()
| * | | | documentation: handling of relative paths by include- and link_directories()Alex Neundorf2013-01-272-6/+5
| | | | | | | | | | | | | | | | | | | | Alex
* | | | | Merge topic 'fix-relocatable-include-dirs'Brad King2013-01-299-30/+97
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 34d1ade Add the INSTALL_PREFIX genex. 3a17197 Generate the _IMPORT_PREFIX in the non-config export file.
| * | | | | Add the INSTALL_PREFIX genex.Stephen Kelly2013-01-279-1/+69
| | | | | |
| * | | | | Generate the _IMPORT_PREFIX in the non-config export file.Stephen Kelly2013-01-271-29/+28
| |/ / / /
* | | | | Merge topic 'fix-automoc-compile-defs'Brad King2013-01-2912-52/+52
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 429e369 Process COMPILE_DEFINITIONS as generator expressions in QtAutomoc. 0e10782 Move GetCompileDefinitions to cmTarget.
| * | | | | Process COMPILE_DEFINITIONS as generator expressions in QtAutomoc.Stephen Kelly2013-01-291-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | Fixes #13493.
| * | | | | Move GetCompileDefinitions to cmTarget.Stephen Kelly2013-01-2911-51/+47
| | | | | |
* | | | | | Merge topic 'PackageConfigHelper_UsrMove'Brad King2013-01-291-4/+22
|\ \ \ \ \ \ | |_|_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4cad848 configure_package_config_file(): extend documentation 37c4bc1 configure_package_config_file(): fix indentation d477414 configure_package_config_file: force absolute paths for usr-move
| * | | | | configure_package_config_file(): extend documentationAlex Neundorf2013-01-241-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | Alex
| * | | | | configure_package_config_file(): fix indentationAlex Neundorf2013-01-241-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a separate commit, so that the previous commit is smaller. Alex
| * | | | | configure_package_config_file: force absolute paths for usr-moveAlex Neundorf2013-01-241-0/+16
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The configure_package_config()_file() macro will now use absolute paths for the PATH_VARS if the Config.cmake file will be installed into /lib(64) or /usr/lib(64), since due to the usr-move filesystem changes Config.cmake files installed there may be found via two paths (once per symlink via /lib(64) and once via /usr/lib ), and in this case relative paths break. Alex
* | | | | CMake Nightly Date StampKitware Robot2013-01-291-1/+1
| | | | |
* | | | | CMake Nightly Date StampKitware Robot2013-01-281-1/+1
| | | | |
* | | | | CMake Nightly Date StampKitware Robot2013-01-271-1/+1
| |/ / / |/| | |
* | | | CMake Nightly Date StampKitware Robot2013-01-261-1/+1
| |_|/ |/| |
* | | Merge topic 'debug-ProcessorCount'Brad King2013-01-252-4/+12
|\ \ \ | | | | | | | | | | | | | | | | | | | | 4d0e2e8 ProcessorCount test: require SystemInformation process to work e03f83f ProcessorCount test: fix path to cmsysTestsCxx executable
| * | | ProcessorCount test: require SystemInformation process to workRolf Eike Beer2013-01-241-1/+8
| | | | | | | | | | | | | | | | | | | | Currently this silently fails on some systems. Make sure those things get noticed so we can fix that.
| * | | ProcessorCount test: fix path to cmsysTestsCxx executableRolf Eike Beer2013-01-242-3/+4
| |/ / | | | | | | | | | | | | Use a generator expression to get the real place of this target instead of guessing it wrong.
* | | Merge topic 'generator-expression-lf'Brad King2013-01-251-4/+5
|\ \ \ | | | | | | | | | | | | | | | | 6c57c31 doc: fix linebreaks in generator expression documentation
| * | | doc: fix linebreaks in generator expression documentationRolf Eike Beer2013-01-241-4/+5
| |/ /
* | | Merge topic 'doc-link-interface'Brad King2013-01-251-1/+3
|\ \ \ | | | | | | | | | | | | | | | | f032fb9 target_link_libraries: Document that new sigs privatize old (#13876)
| * | | target_link_libraries: Document that new sigs privatize old (#13876)Brad King2013-01-241-1/+3
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Explain in the documentation for the legacy signature target_link_libraries(foo bar) that the other signatures like target_link_libraries(foo LINK_INTERFACE_LIBRARIES ...) target_link_libraries(foo LINK_PRIVATE ...) will set the LINK_INTERFACE_LIBRARIES target property and therefore make libraries specified only by the legacy signature private.
* | | Merge topic 'compatible-interface-strings'Brad King2013-01-2522-48/+303
|\ \ \ | | | | | | | | | | | | | | | | | | | | 2fb2c32 Add the COMPATIBLE_INTERFACE_STRING property. cd66b91 Make calculation of link-interface-dependent properties type-sensitive.
| * | | Add the COMPATIBLE_INTERFACE_STRING property.Stephen Kelly2013-01-2422-1/+186
| | | |
| * | | Make calculation of link-interface-dependent properties type-sensitive.Stephen Kelly2013-01-241-48/+118
| |/ /
* | | CMake Nightly Date StampKitware Robot2013-01-251-1/+1
|/ /
* | Merge topic 'fix-COMPATIBLE_INTERFACE-link-libraries'Brad King2013-01-245-3/+48
|\ \ | | | | | | | | | | | | 6fbe3ce Exclude the LINK_LIBRARIES related properties from INTERFACE evaluation.
| * | Exclude the LINK_LIBRARIES related properties from INTERFACE evaluation.Stephen Kelly2013-01-245-3/+48
| | | | | | | | | | | | | | | | | | These interface-related link-libraries properties are used to determine the value of the other INTERFACE properties, so we were getting infinite recursion and segfaults otherwise.
* | | Merge topic 'cmMakefile-comment-typos'Brad King2013-01-241-3/+3
|\ \ \ | | | | | | | | | | | | | | | | 3853a6c spell: fix a few typos in comments
| * | | spell: fix a few typos in commentsYury G. Kudryashov2013-01-231-3/+3
| | | |
* | | | CMake Nightly Date StampKitware Robot2013-01-241-1/+1
| |/ / |/| |
* | | Merge topic 'disallow-IMPORTED-interface-porcelain'Brad King2013-01-2312-61/+15
|\ \ \ | | | | | | | | | | | | | | | | | | | | b98d14d Disallow porcelain to populate includes and defines of IMPORTED targets. 48a4cf2 Revert "Allow target_link_libraries with IMPORTED targets."
| * | | Disallow porcelain to populate includes and defines of IMPORTED targets.Stephen Kelly2013-01-2110-44/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With similar reasoning to the parent commit, as downstreams, we can't determine what $<CONFIG> generator expressions would be appropriate. Upstream would have populated the INTERFACE_INCLUDE_DIRECTORIES with config-specific generator expressions, possibly appropriate for their DEBUG_CONFIGURATIONS. In theory, if we would add include directories for a DEBUG intent, we would have to match the upstream configurations for that. Rather than attempting to discover the appropriate configurations at this time, simplify the feature instead. The use of IMPORTED targets with these commands could still be added in the future if targets would export their DEBUG_CONFIGURATIONS somehow.
| * | | Revert "Allow target_link_libraries with IMPORTED targets."Stephen Kelly2013-01-212-17/+0
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 9cfe4f1b769597bd9ba179eba46572a9df27f64c. It turns out that correctly adding the content to the IMPORTED_LINK_INTERFACE_LIBARIES_<CONFIG> of an upstream target from the buildsystem of a downstream project is not simple. If upstream had added the INTERFACE content, the config-specific properties would be determined by the DEBUG_CONFIGURATIONS of upstream. As downstream, we don't have any information about what the DEBUG_CONFIGURATIONS of upstream were, so we can't determine which configuration-specific properties to populate. The best we can do is add it to all of them or add it to the ones downstream considers to be DEBUG_CONFIGURATIONS, neither of which is a good solution. So, removing the porcelain API for that is the best approach. A human can still determine which properties to populate and use the set_property API to populate the desired properies. Another solution to this would be for upstream targets to publish what they consider DEBUG_CONFIGURATIONS, but that can be added in a future release.
* | | Merge topic 'clean-include-dirs-debugging'Brad King2013-01-2310-63/+122
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6063fef Output include directories as LOG messages, not warnings. aa66748 Specify the target whose includes are being listed. d70204a Only output includes once after the start of 'generate-time' when debugging. 0d46e9a Store includes from the same include_directories call together.
| * | | Output include directories as LOG messages, not warnings.Stephen Kelly2013-01-212-4/+8
| | | |
| * | | Specify the target whose includes are being listed.Stephen Kelly2013-01-212-6/+6
| | | |
| * | | Only output includes once after the start of 'generate-time' when debugging.Stephen Kelly2013-01-215-1/+17
| | | | | | | | | | | | | | | | | | | | | | | | During configure-time, GetIncludeDirectories may be called too, for example if using the export() command. As the content can be different, it should be output each time then.
| * | | Store includes from the same include_directories call together.Stephen Kelly2013-01-216-52/+91
| | | | | | | | | | | | | | | | | | | | | | | | Otherwise, we get a separate IncludeDirectoriesEntry for each include, and that causes unnecessary and confusing splitting in the output when debugging the INCLUDE_DIRECTORIES property.
generated by cgit v0.12 at 2025-02-08 04:52:59 (GMT)