summaryrefslogtreecommitdiffstats
path: root/Help/prop_tgt
Commit message (Collapse)AuthorAgeFilesLines
* Update documentation about bundle extensionsGregor Jasny2016-07-221-3/+4
|
* Windows: Honor WINDOWS_EXPORT_ALL_SYMBOLS for executables with exportsYury Zhuravlev2016-07-111-2/+3
| | | | | For executables with ENABLE_EXPORTS set, export all symbols when instructed to do so by WINDOWS_EXPORT_ALL_SYMBOLS.
* Merge topic 'doc-cross-reference-lang-standard-and-extensions'Brad King2016-06-284-2/+8
|\ | | | | | | | | c6a077d6 Help: Cross reference CXX_STANDARD and CXX_EXTENSIONS (#16162)
| * Help: Cross reference CXX_STANDARD and CXX_EXTENSIONS (#16162)Gregor Jasny2016-06-284-2/+8
| |
* | Merge topic 'doc-osx-versions'Brad King2016-06-273-13/+43
|\ \ | | | | | | | | | | | | 00caa1dd Help: Describe VERSION and SOVERSION meanings for Mach-O binaries
| * | Help: Describe VERSION and SOVERSION meanings for Mach-O binariesBartosz Kosiorek2016-06-233-13/+43
| |/
* | VS: Add VS_SDK_REFERENCES target property to reference external SDKsGilles Khouzam2016-06-221-0/+7
| | | | | | | | | | Allow one to specify external SDK references such as `Microsoft.AdMediatorWindows81, Version=1.0`.
* | Add options to run `ldd -u -r` as a "link-what-you-use" toolBill Hoffman2016-06-171-0/+15
|/ | | | | | | Create a LINK_WHAT_YOU_USE target property and corresponding CMAKE_LINK_WHAT_YOU_USE variable to enable this behavior. Extend link commands by running `ldd -u -r` to detect shared libraries that are linked but not needed.
* CustomCommandGenerator: Add support for CROSSCOMPILING_EMULATORJean-Christophe Fillion-Robin2016-05-091-3/+4
| | | | | | Teach the `add_custom_command` and `add_custom_target' commands to substitute argv0 with the crosscompiling emulator if it is a target with the `CROSSCOMPILING_EMULATOR` property set.
* Help: Hyperlink propertiesGregor Jasny2016-04-271-5/+5
|
* Autogen: Check added for name collisions of generated moc filesSebastian Holtermann2016-04-221-1/+7
| | | | | The test exits with an error if two or more source files would generate the same moc file.
* Help: Improve AUTOMOC documentation layoutBrad King2016-04-221-16/+23
|
* Add options to run clang-tidy with the compilerDaniel Pfeifer2016-04-131-0/+13
| | | | | | Create a <LANG>_CLANG_TIDY target property (initialized by a CMAKE_<LANG>_CLANG_TIDY variable) to specify a clang-tidy command line to be run along with the compiler.
* Fix spelling typos in comments and documentation (#16037)Felix Geyer2016-03-292-2/+2
| | | | | The Debian package checker tool (lintian) detected several typos in CMake.
* VS: Optionally generate remote directory for WinCE projectsAndrej Bosik2016-03-151-0/+18
| | | | | | | Teach the VS 2008 and 2005 generators to set the `RemoteDirectory` in `DeploymentTool` and the `RemoteExecutable` in `DebuggerTool`. Use a `DEPLOYMENT_REMOTE_DIRECTORY` target property to specify the value.
* Drop Visual Studio 6 generatorBrad King2016-03-093-8/+1
| | | | | | This generator has been deprecated since CMake 3.3. Remove it. Update documentation, modules, and tests to drop content specific to this generator.
* VS: Add option to set `ConfigurationType` of a .vcxproj fileFabian Otto2016-02-261-0/+10
| | | | | | Add a VS_CONFIGURATION_TYPE target property to set this value explicitly. This is useful to build a Windows Kernel Mode Driver, for example.
* Xcode: Add support for combined install on iOSRuslan Baratov2015-12-101-0/+11
| | | | | | | | | | | | This patch solves the problem of installing both: Device and Simulator libraries on iOS. Before only one of them was installed. If the IOS_INSTALL_COMBINED property is set on a target, a special install hook will be activated which builds the corresponding target and combines both at the install location. The original patch was contributed by Ruslan Baratov, and polished by Gregor Jasny.
* iOS: Fix framework resource directory layout (#15848)Bartosz Kosiorek2015-12-033-12/+62
| | | | | | | | A typical iOS application bundle (also Framework Bundle) contains the application executable and any resources used by the application (for instance, the application icon, other images, and localized content) in the top-level bundle directory. The same rule applies to Framework Bundles.
* Help: Update documentation to reflect support for iOSBartosz Kosiorek2015-11-2313-44/+67
| | | | Many of our interfaces documented for OS X also work for iOS.
* Merge topic 'macosx_rpath-clarify-doc'Brad King2015-11-021-5/+10
|\ | | | | | | | | f8eb72fe Help: Clarify documentation for MACOSX_RPATH variable.
| * Help: Clarify documentation for MACOSX_RPATH variable.Clinton Stimpson2015-11-021-5/+10
| |
* | Help: Document target properties setting Info.plist fields (#15820)Brad King2015-10-302-29/+37
|/ | | | | Format the documentation of MACOSX_{BUNDLE,FRAMEWORK}_INFO_PLIST and specify for each property what field in the Info.plist file it sets.
* VS: Add support for Windows 10 Universal (Store) ApplicationsGilles Khouzam2015-10-055-0/+46
| | | | | | | | | | | | | | | | Teach the VS 2015 generator to support WindowsStore 10.0 applications. Add target properties to customize them: * VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION: Specifies the minimum version of the OS that the project can target. * VS_DESKTOP_EXTENSIONS_VERSION, VS_MOBILE_EXTENSIONS_VERSIONS, VS_IOT_EXTENSIONS_VERSION: Add a reference to the version of the SDK specified to the target allowing to target the extended functionality in a universal project. * VS_IOT_STARTUP_TASK: Specifies that the target should be built as an IOT continuous background task.
* CMP0065: Restrict the use of CMAKE_SHARED_LIBRARY_LINK_<LANG>_FLAGSChuck Atkins2015-09-211-1/+4
| | | | | This new policy restricts the addition of the shared library link flags to executables only when the ENABLE_EXPORTS property is set to True.
* Do not set SONAME for MODULE library targets (#15705)Felix Geyer2015-08-201-3/+3
| | | | | The SONAME field is only useful for shared libraries that application link against.
* Merge topic 'OUTPUT_DIRECTORY-genex'Brad King2015-08-134-2/+14
|\ | | | | | | | | | | d25819bc Add generator expression support to OUTPUT_DIRECTORY target properties e36a05fd cmTarget: Detect and diagnose recursion in GetOutputInfo
| * Add generator expression support to OUTPUT_DIRECTORY target propertiesRobert Goulet2015-08-124-2/+14
| | | | | | | | | | | | | | If {ARCHIVE,LIBRARY,RUNTIME}_OUTPUT_DIRECTORY is set with a genex then do not add the per-config subdirectory on multi-config generators. This will allow projects to use $<CONFIG> to place the per-config part of the directory path somewhere other than the end.
* | Allow LINK_SEARCH_{START,END}_STATIC props to have default values.Chuck Atkins2015-08-132-3/+12
|/ | | | | | Use the CMAKE_LINK_SEARCH_START_STATIC and CMAKE_LINK_SEARCH_END_STATIC variables to initialize the LINK_SEARCH_START_STATIC and LINK_SEARCH_END_STATIC target properties respectively.
* Add SOURCE_DIR and BINARY_DIR target propertiesClifford Yapp2015-07-212-0/+12
| | | | | This will allow project code to recover the directory information about where a target was created.
* Merge topic 'vs-nsight-tegra-attributes'Brad King2015-07-1514-0/+148
|\ | | | | | | | | 8c0afaf4 VS: Add more Nsight Tegra generator Android property settings
| * VS: Add more Nsight Tegra generator Android property settingsMikhail Filimonov2015-07-1414-0/+148
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Extend the Nsight Tegra project generator to add bunch of properties with the backing variables to fine-tune the generated projects. Add target properties that map to all "Configuration" PropertyGroups for each configuration: * ANDROID_ARCH * ANDROID_STL_TYPE Add target properties that map to the AntBuild section of vcxproj files: * ANDROID_ANT_ADDITIONAL_OPTIONS * ANDROID_ASSETS_DIRECTORIES * ANDROID_JAR_DEPENDENCIES * ANDROID_JAR_DIRECTORIES * ANDROID_JAVA_SOURCE_DIR * ANDROID_NATIVE_LIB_DEPENDENCIES * ANDROID_NATIVE_LIB_DIRECTORIES * ANDROID_PROCESS_MAX * ANDROID_PROGUARD * ANDROID_PROGUARD_CONFIG_PATH * ANDROID_SECURE_PROPS_PATH * ANDROID_SKIP_ANT_STEP Reviewed-by: Dmitry Polyanitsa <dpolyanitsa@nvidia.com>
* | Help: Document Apple Framework creation with an example (#15651)Brad King2015-07-142-1/+8
|/
* Add generator expression support to OUTPUT_NAME target propertyRobert Goulet2015-07-091-0/+3
|
* Help: Improve OUTPUT_NAME documentation formattingBrad King2015-07-093-3/+15
| | | | Also link to its variants.
* Windows: Optionally generate DLL module definition files automaticallyBill Hoffman2015-07-061-0/+18
| | | | | | | Create target property WINDOWS_EXPORT_ALL_SYMBOLS to automatically generate a module definition file from MS-compatible .obj files and give it to the linker in order to export all symbols from the .dll part of a SHARED library.
* Add options to launch the compiler through tools like ccache or distccBill Hoffman2015-06-151-0/+13
| | | | | | | | | | | | | Create a <LANG>_COMPILER_LAUNCHER target property (initialized by a CMAKE_<LANG>_COMPILER_LAUNCHER variable) to specify a compiler launcher tool. This will supersede the CMAKE_<LANG>_COMPILER_ARG1 approach to using such tools. The old approach set CMAKE_<LANG>_COMPILER to the launcher tool while the new approach leaves this variable set to the actual compiler. Implement this property for Makefile and Ninja generators. It cannot be implemented for VS or Xcode generators as the IDE build tools offer no such hooks.
* Honor visibility properties for all target types (#15556)Brad King2015-05-262-4/+8
| | | | | | | | | | | | | | | | The <LANG>_VISIBILITY_PRESET and VISIBILITY_INLINES_HIDDEN were first merged in commit v2.8.12~322 (Merge topic 'VISIBILITY_PRESET-property', 2013-06-05) but worked only for shared libraries and executables with exports. Prior to commit v3.0.0-rc1~581^2 (GenerateExportHeader: Deprecate add_compiler_export_flags function., 2013-09-02) the add_compiler_export_flags function was used to add visibility flags to all targets. The visibility flags are useful for sources in all target types because they may be later linked into shared libraries or executables with exports. Introduce policy CMP0063 to enable them for all target types while preserving compatibility with existing projects that do not expect this.
* Help: Format visibility property and variable documentationBrad King2015-05-222-8/+9
| | | | Add reStructuredText markup appropriately.
* Add options to run include-what-you-use with the compilerBrad King2015-05-191-0/+13
| | | | | | Create a <LANG>_INCLUDE_WHAT_YOU_USE target property (initialized by a CMAKE_<LANG>_INCLUDE_WHAT_YOU_USE variable) to specify an IWYU command line to be run along with the compiler.
* Help: Revise buildsystem artifact file type documentation (#15539)Brad King2015-04-2915-41/+53
| | | | | | Add sections to the cmake-buildsystem(7) manual and cross-reference them with relevant variables and target properties. This avoids duplicating the information and allows it to be more detailed.
* Help: Clarify PDB_NAME fallback behavior (#15518)Brad King2015-04-171-1/+2
| | | | It uses the OUTPUT_NAME if set, not always the target name.
* 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>
generated by cgit v0.12 at 2025-01-04 02:42:28 (GMT)