summaryrefslogtreecommitdiffstats
path: root/Help/prop_tgt
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'emulator-property'Brad King2015-04-081-0/+6
|\ | | | | | | | | | | | | | | 1975d53a Help: Add notes for topic 'emulator-property' 9160d6c2 TestGenerator: Add CROSSCOMPILING_EMULATOR support. e942526b try_run: Use CMAKE_CROSSCOMPILING_EMULATOR. 579c4bec Properties: Add CROSSCOMPILING_EMULATOR target property.
| * TestGenerator: Add CROSSCOMPILING_EMULATOR support.Matt McCormick2015-04-081-1/+3
| | | | | | | | | | | | Prefix test commands with the CROSSCOMPILING_EMULATOR property for target executables. This allows test suites to be run on the host when crosscompiling.
| * Properties: Add CROSSCOMPILING_EMULATOR target property.Matt McCormick2015-04-071-0/+4
| | | | | | | | | | | | | | Add CROSSCOMPILING_EMULATOR target property for executables. This is used by subsequent patches to run exectuables created for the target system when crosscompiling. The property is initialized by the CMAKE_CROSSCOMPILING_EMULATOR variable when defined.
* | Help: Document supported compilers in cmake-compile-features.7Robert Maynard2015-04-078-8/+8
|/ | | | | | | Extend sentences in other documentation linking to this manual to say that it has a list of supported compilers. Co-Author: Brad King <brad.king@kitware.com>
* Help: Place relocatable package notes in their own subsectionsBrad King2015-04-034-0/+12
| | | | | | | These notes apply only for the use case of creating a package for redistribution on machines other than that where it is built. Clarify this to readers by placing the discussion in dedicated sections titled accordingly.
* Help: Refine COMPILE_OPTIONS property documentationBrad King2015-03-311-4/+5
| | | | | | Make wording of the directory and target properties more consitent and complementary. Specify that the value is a ";-list" with a link to the cmake-language(7) manual section on lists.
* OS X: Add handling for XCTest bundlesGregor Jasny2015-03-231-0/+13
| | | | | | | | | | An XCTest bundle is a CFBundle with a special product-type and bundle extension. For more information about XCTest visit the Mac Developer library at: http://developer.apple.com/library/mac/documentation/DeveloperTools/Conceptual/testing_with_xcode/ Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
* Xcode: Teach XCODE_ATTRIBUTE target properties about generator expressionsGregor Jasny2015-02-121-0/+6
| | | | Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
* Allow export of targets with INTERFACE_SOURCES.Stephen Kelly2015-02-101-4/+0
| | | | | | Use the same rules for paths in source and binary dirs in installed INTERFACE_SOURCES as are used for INTERFACE_INCLUDE_DIRECTORIES.
* Features: Define meaning for no language standard defaultBrad King2015-01-294-4/+8
| | | | | | | | | | | | Define an empty string in CMAKE_<LANG>_STANDARD_DEFAULT to mean that the toolchain has no notion of lanuage standard levels. In this case the <LANG>_STANDARD[_REQUIRED] properties will have no effect. Update the RunCMake.CompileFeatures test to exclude the LinkImplementationFeatureCycle test when there is no standard default. It can never fail because no use of specific features will adjust the CXX_STANDARD level required for any target since the standard levels have no meaning in this case.
* Help: Clarify INTERFACE_SYSTEM_INCLUDE_DIRECTORIES documentation.Stephen Kelly2015-01-221-2/+9
|
* Merge topic 'doc-CXX_STANDARD-14'Brad King2015-01-101-1/+1
|\ | | | | | | | | 72a0d6df Help: Document valid 14 value for CXX_STANDARD. (#15339)
| * Help: Document valid 14 value for CXX_STANDARD. (#15339)Stephen Kelly2015-01-081-1/+1
| | | | | | | | | | | | Support was added in commit v3.1.0-rc1~475^2 (Features: Add support for C++14 features., 2014-05-06), but the documentation for this property was not amended.
* | Merge topic 'vs-nsight-tegra-min-api'Brad King2014-12-181-0/+7
|\ \ | | | | | | | | | | | | eeaa25e5 Add 'ANDROID_API_MIN' target property to set Android Target MIN API
| * | Add 'ANDROID_API_MIN' target property to set Android Target MIN APIDmitry Polyanitsa2014-12-171-0/+7
| | | | | | | | | | | | | | | | | | Also add a 'CMAKE_ANDROID_API_MIN' variable to set the property default. Teach the VS generator to write the MIN API value into Nsight Tegra project files.
* | | Merge topic 'doc-INTERFACE-target-type'Brad King2014-12-181-1/+2
|\ \ \ | |/ / |/| / | |/ | | 473446ab Help: Add INTERFACE_LIBRARY to TYPE target property documentation
| * Help: Add INTERFACE_LIBRARY to TYPE target property documentationTim Blechmann2014-12-171-1/+2
| |
| * Merge branch 'doc-Nsight-Tegra-toolchain' into releaseBrad King2014-12-031-0/+4
| |\
* | \ Merge topic 'doc-Nsight-Tegra-toolchain'Brad King2014-12-031-0/+4
|\ \ \ | | |/ | |/| | | | | | | 23e2bd7e Help: Document Nsight Tegra toolchain configuration (#15276)
| * | Help: Document Nsight Tegra toolchain configuration (#15276)Brad King2014-12-021-0/+4
| | |
* | | Merge topic 'target-sources-error-conditions'Brad King2014-12-011-0/+4
|\ \ \ | | |/ | |/| | | | | | | | | | | | | 8a75c7ef Help: Document the export limitation of INTERFACE_SOURCES. e1348056 Export: Disallow export of targets with INTERFACE_SOURCES bb5905bb cmTarget: Don't allow relative paths in INTERFACE_SOURCES
| * | Help: Document the export limitation of INTERFACE_SOURCES.Stephen Kelly2014-11-291-0/+4
| |/
* | Help: Warn that paths should not be used in INTERFACE_ build properties.Stephen Kelly2014-11-254-0/+12
| |
* | Help: Use a property-specific command instead of the generic one.Stephen Kelly2014-11-221-2/+2
| |
* | Help: Make remaining build property docs consistent.Stephen Kelly2014-11-222-7/+16
| | | | | | | | | | These help entries are different enough that they can not use the generic template.
* | Help: Link to target_link_libraries from target properies.Stephen Kelly2014-11-222-2/+4
| |
* | Help: Format the LINK_INTERFACE_LIBRARIES target properies.Stephen Kelly2014-11-222-12/+15
| |
* | Help: Unify the help text of INTERFACE_ build properties.Stephen Kelly2014-11-225-51/+41
|/
* Help: Document CMAKE_XCODE_ATTRIBUTE_<an-attribute> variable (#15215)Brad King2014-10-221-0/+3
|
* Add 'ANDROID_API' target property to set Android Target APIBrad King2014-09-301-0/+7
| | | | Also add a 'CMAKE_ANDROID_API' variable to set the property default.
* Add 'ANDROID_GUI' target property to mark Android applicationsBrad King2014-09-291-0/+9
| | | | | | | Also add a 'CMAKE_ANDROID_GUI' variable to set the property default so a project can easily make all executables Android applications. An Android application executable file has the same extension as a shared library (.so).
* VS: Do not compile C sources as WinRT (#15100)Brad King2014-09-021-3/+0
| | | | | | | | The MSVC /ZW flag is valid only for C++ sources. Whenever we enable CompileAsWinRT for the whole target, disable it for all C sources. Update the documentation of VS_WINRT_COMPONENT to drop the statement about undefined behavior for non-C++ sources, because it is now defined as expected.
* VS: Add VS_WINRT_COMPONENT property to enable CompileAsWinRTGilles Khouzam2014-08-212-3/+16
| | | | | | | | Deprecate VS_WINRT_EXTENSIONS and document VS_WINRT_COMPONENT as for VS generators only. Also define _WINRT_DLL in SHARED libraries in order to get a .lib produced. Inspired-by: Paul Annetts <paul@lightunobscured.com>
* Help: Document deprecated properties.Nils Gladitz2014-07-211-0/+2
| | | | | | Document the COMPILE_DEFINITIONS_<Config> properties as deprecated. Add new sections for deprecated properties and move POST_INSTALL_SCRIPT and PRE_INSTALL_SCRIPT there as well.
* Merge topic 'doc-include-dir-props'Brad King2014-06-031-0/+18
|\ | | | | | | | | 907e422b Help: Explain build/install-tree include dirs in more places (#14946)
| * Help: Explain build/install-tree include dirs in more places (#14946)Brad King2014-06-021-0/+18
| | | | | | | | | | | | | | | | | | | | | | Explain how to use $<BUILD_INTERFACE> and $<INSTALL_INTERFACE> directly in the documentation of the target_include_directories command and INTERFACE_INCLUDE_DIRECTORIES target property. Otherwise readers need to notice the link to the cmake-buildsystem(7) manual and find the example in that to understand the need for these expressions. Also fix the explanation in cmake-buildsystem(7) to not claim that relative paths may be used inside a BUILD_INTERFACE expression.
* | Features: Enable compiler extensions by default.Stephen Kelly2014-05-314-8/+10
| | | | | | | | | | | | | | | | | | | | | | Compilers enable their extensions by default, and disabling them implicitly can lead to results which are surprising or non-obvious to debug. http://public.kitware.com/pipermail/cmake-developers/2014-May/010575.html http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/10214 https://www.mail-archive.com/cmake-developers@cmake.org/msg10116.html (Compiler feature extensions by default, 29 May 2014)
* | Help: Add a manual for compiler feature control.Stephen Kelly2014-05-278-2/+23
| | | | | | | | | | | | | | | | Link to it from the documentation of related properties, variables and commands. Extend the cmake-developer(7) documentation with notes on extending feature support for compilers.
* | Features: Add missing variable reference in docs.Stephen Kelly2014-05-222-0/+8
| |
* | Features: Extend concept to C language.Stephen Kelly2014-05-143-0/+49
| | | | | | | | | | | | | | | | | | | | | | Add properties and variables corresponding to CXX equivalents. Add features for c_function_prototypes (C90), c_restrict (C99), c_variadic_macros (C99) and c_static_assert (C11). This feature set can be extended later. Add a <PREFIX>_RESTRICT symbol define to WriteCompilerDetectionHeader to conditionally represent the c_restrict feature.
* | cmTarget: Add CXX_STANDARD_REQUIRED to control decay.Stephen Kelly2014-05-072-1/+16
| |
* | Features: Decay language flag if requested is not available.Stephen Kelly2014-05-071-2/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use the highest standard compile flags available if requested language version is too new. This supports use-cases like set(CMAKE_CXX_STANDARD 14) # Compiled with -std=c++11 with GNU 4.7, which has no -std=c++14 # or equivalent flag add_executable(main main.cpp) This can be used in combination with preprocessor defines which communicate the availability of certain language features for optional use.
* | cmTarget: Transitively evaluate compiler features.Stephen Kelly2014-04-071-0/+14
| | | | | | | | | | | | | | | | | | | | | | Extend the interface of the target_compile_features command with PUBLIC and INTERFACE keywords. Populate the INTERFACE_COMPILER_FEATURES target property if they are set. Consume the INTERFACE_COMPILER_FEATURES target property from linked dependent targets to determine the final required compiler features and the compile flag, if needed. Use the same pattern of origin-debugging which is used for other build properties.
* | cmTarget: Allow populating COMPILE_FEATURES using generator expressions.Stephen Kelly2014-04-071-0/+4
| | | | | | | | | | | | Delay validation of the content as a feature if it contains a generator expression. It will be checked again at generate-time after evaluation.
* | cmTarget: Add COMPILE_FEATURES target property.Stephen Kelly2014-04-071-0/+7
| | | | | | | | | | | | | | Use the contents of it to upgrade the CXX_STANDARD target property, if appropriate. This will have the effect of adding the -std=c++11 compile flag or other language specification on GNU when that is needed for the feature.
* | cmTarget: Add CXX_STANDARD and CXX_EXTENSION target properties.Stephen Kelly2014-04-072-0/+22
| | | | | | | | | | These are used to determine whether to add -std=c++11, -std=gnu++11 etc flags on the compile line.
* | Make the SOURCES target property writable.Stephen Kelly2014-04-021-2/+1
| |
* | cmTarget: Allow transitive evaluation of SOURCES property.Stephen Kelly2014-04-021-0/+15
| | | | | | | | | | | | | | Extend the cmGeneratorExpressionDAGChecker with an interface returning the name of the top target. Use that to determine when there is a DAG violation, as required by the RunCMake.Languages tests.
* | MSVC: Add properties to configure compiler PDB files (#14762)Brad King2014-02-2610-1/+63
| | | | | | | | | | | | | | | | | | | | Since commit v2.8.12~437^2~2 (VS: Separate compiler and linker PDB files 2013-04-05) we no longer set /Fd with the PDB_NAME or PDB_OUTPUT_DIRECTORY properties. Those properties now exclusively handle linker PDB files. Since STATIC libraries do not link their compiler PDB file becomes more important. Add new target properties "COMPILE_PDB_NAME[_<CONFIG>]" and "COMPILE_PDB_OUTPUT_DIRECTORY[_<CONFIG>]" to specify the compiler PDB file location and pass the value to the MSVC /Fd option.
* | Help: Refactor PDB_NAME and PDB_OUTPUT_DIRECTORY docsBrad King2014-02-245-13/+9
|/ | | | | | | Move the note about VS 6 into the PDB_NOTE.txt common include file and include it from the per-config properties too. Also re-word the note to clarify the separate compiler and linker flags involved and state explicitly that compiler flags are not affected.
generated by cgit v0.12 at 2024-12-26 17:25:31 (GMT)