summaryrefslogtreecommitdiffstats
path: root/Source/cmTargetCompileDefinitionsCommand.h
Commit message (Collapse)AuthorAgeFilesLines
* Simplify CMake per-source license noticesBrad King2016-09-271-12/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | Per-source copyright/license notice headers that spell out copyright holder names and years are hard to maintain and often out-of-date or plain wrong. Precise contributor information is already maintained automatically by the version control tool. Ultimately it is the receiver of a file who is responsible for determining its licensing status, and per-source notices are merely a convenience. Therefore it is simpler and more accurate for each source to have a generic notice of the license name and references to more detailed information on copyright holders and full license terms. Our `Copyright.txt` file now contains a list of Contributors whose names appeared source-level copyright notices. It also references version control history for more precise information. Therefore we no longer need to spell out the list of Contributors in each source file notice. Replace CMake per-source copyright/license notice headers with a short description of the license and links to `Copyright.txt` and online information available from "https://cmake.org/licensing". The online URL also handles cases of modules being copied out of our source into other projects, so we can drop our notices about replacing links with full license text. Run the `Utilities/Scripts/filter-notices.bash` script to perform the majority of the replacements mechanically. Manually fix up shebang lines and trailing newlines in a few files. Manually update the notices in a few files that the script does not handle.
* mark functions with CM_OVERRIDEDaniel Pfeifer2016-06-271-10/+16
|
* Revise C++ coding style using clang-formatKitware Robot2016-05-161-11/+8
| | | | | | | | | | | | | Run the `Utilities/Scripts/clang-format.bash` script to update all our C++ code to a new style defined by `.clang-format`. Use `clang-format` version 3.8. * If you reached this commit for a line in `git blame`, re-run the blame operation starting at the parent of this commit to see older history for the content. * See the parent commit for instructions to rebase a change across this style transition commit.
* cmTargetPropCommandBase: Change the interface to return bool.Stephen Kelly2014-04-071-1/+1
| | | | | This is needed for the target_compile_features command, which may fail at configure time if an invalid feature is specified.
* stringapi: Command namesBen Boeckel2014-03-081-1/+1
|
* Drop builtin command documentationBrad King2013-10-161-35/+0
| | | | | Drop all GetTerseDocumentation and GetFullDocumentation methods from commands. The command documentation is now in Help/command/*.rst files.
* Remove the LINK_LANGUAGE generator expression.Stephen Kelly2013-07-241-1/+0
| | | | | | | | | | | It accepted an optional argument to test for equality, but no way to get the linker language of a particular target. TARGET_PROPERTY provides this flexibility and STREQUAL provides the necessary API for equality test. Extend the CompileDefinitions test to cover accessing the property of another target.
* Add a SYSTEM parameter to target_include_directories (#14180)Stephen Kelly2013-07-021-1/+1
| | | | | | This is similar to the include_directories(SYSTEM) signature in that it allows telling the compiler to ignore warnings from such headers.
* Add $<LINK_LANGUAGE> generator expressionStephen Kelly2013-05-241-0/+1
| | | | | | They can't be used when evaluating link libraries, but they can be used for include directories and compile definitions. Later they can be used for compile options.
* Fix new target commands documentation.Stephen Kelly2013-03-251-4/+2
| | | | | | | | | | | | | | The target_include_directories and target_compile_defintions commands accepted targets as arguments until commit f6b16d4b (Don't allow targets args in the new target commands., 2013-01-29). This followed from discussion on the mailing list (target_include_directories() accepts only absolute paths ?, 2013-01-28): http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/5925/focus=5948 http://public.kitware.com/pipermail/cmake-developers/2013-January/006301.html It was also decided to allow relative paths in target_include_directories().
* Fix use of cmTypeMacro in new command classesBrad King2013-01-311-1/+1
| | | | | | | | Both commit 8a37ebec (Add the target_include_directories command, 2013-01-01) and commit fc61a7a7 (Add the target_compile_definitions command, 2013-01-08) added command implementations deriving from the new cmTargetPropCommandBase class. Fix cmTypeMacro declarations of the inheritance relationship.
* Make subclasses responsible for joining content.Stephen Kelly2013-01-291-1/+3
| | | | | 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-291-5/+0
|
* Disallow porcelain to populate includes and defines of IMPORTED targets.Stephen Kelly2013-01-211-3/+2
| | | | | | | | | | | | | | | | 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.
* Document the use of generator expressions in new commands.Stephen Kelly2013-01-131-0/+3
|
* Add the target_compile_definitions command.Stephen Kelly2013-01-101-0/+91
This is a convenience API to populate the corresponding properties.
generated by cgit v0.12 at 2024-12-28 19:31:18 (GMT)