summaryrefslogtreecommitdiffstats
path: root/Help/manual
Commit message (Collapse)AuthorAgeFilesLines
...
| * Link libraries by full path even in implicit directoriesBrad King2015-04-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When CMP0003 was first introduced we wanted to link all libraries by full path. However, some projects had problems on platforms where find_library would find /usr/lib/libfoo.so when the project really wanted to link to /usr/lib/<arch>/libfoo.so and had been working by accident because pre-CMP0003 behavior used -lfoo to link. We first tried to address that in commit v2.6.0~440 (Teach find_library to avoid returning library paths in system directories, 2008-01-23) by returning just "foo" for libraries in implicit link directories. This caused problems for projects expecting find_library to always return a full path. We ended up using the solution in commit v2.6.0~366 (... switch library paths found in implicit link directories to use -l, 2008-01-31). However, the special case for libraries in implicit link directories has also proven problematic and confusing. Introduce policy CMP0060 to switch to linking all libraries by full path even if they are in implicit link directories. Explain in the policy documentation the factors that led to the original approach and now to this approach.
| * Help: Add link target for Find Modules section of cmake-developer.7Brad King2015-04-071-0/+1
| |
* | Merge topic 'emulator-property'Brad King2015-04-082-0/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | 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.
| * | Properties: Add CROSSCOMPILING_EMULATOR target property.Matt McCormick2015-04-072-0/+2
| |/ | | | | | | | | | | | | 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-072-1/+15
|/ | | | | | | 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>
* Merge topic 'improve-properties-help'Brad King2015-04-061-1/+15
|\ | | | | | | | | | | | | | | | | 6f82b5e8 Help: Link to properties in set_tests_properties. 66f5af29 Help: Link to properties in set_directory_properties docs. f7dd3f7c Help: Add link in set_source_files_properties command docs. 3b256173 Help: Shorten too-long title marker. 8fc3a2fb Help: Add references to cmake-property sections.
| * Help: Shorten too-long title marker.Stephen Kelly2015-04-041-1/+1
| |
| * Help: Add references to cmake-property sections.Stephen Kelly2015-04-041-0/+14
| |
* | Help: Clarify manual reference for generator namesNils Gladitz2015-04-041-1/+1
|/
* Merge topic 'vs-xaml'Brad King2015-04-031-0/+1
|\ | | | | | | | | 01a9ab0d VS: Add support for XAML source files
| * VS: Add support for XAML source filesGilles Khouzam2015-04-031-0/+1
| | | | | | | | | | | | | | | | XAML files are by default of type Page in the vcxproj and can be overriden by setting the VS_XAML_TYPE property. The .cpp and .h file of the same name are automatically added as depending on the XAML file. New VSXaml test builds a basic XAML WindowsStore 8.1 app with VS2013.
* | Merge topic 'doc-relocatable-usage-requirements'Brad King2015-04-032-70/+113
|\ \ | |/ |/| | | | | | | | | | | | | 3af13782 Help: Update discussion of relocable packages in cmake-packages(7) 227992c3 Help: Reorganize and refine discussion of relocatable packages 031d894f Help: Place relocatable package notes in their own subsections 6e331ce9 Help: Fix typo in cmake-packages(7) manual ba9b9d79 Help: Fix syntax in non-relocatable usage requirements example
| * Help: Update discussion of relocable packages in cmake-packages(7)Brad King2015-04-031-20/+46
| | | | | | | | | | | | | | | | | | | | Explain at the beginning of the section the requirements for a package to be relocatable to justify the rest of the section content. Generalize example to use fictional package names instead of real ones, especially because FindBoost provides no alternative yet. Reword the discussion to represent the preferred approach as "ideal" but also suggest workarounds when find modules do not provide the imported targets.
| * Help: Reorganize and refine discussion of relocatable packagesBrad King2015-04-032-70/+87
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Re-organize the content added to the cmake-packages(7) manual by * commit v3.0.0-rc1~184^2 (Help: Document export(EXPORT) in the cmake-packages manual, 2013-12-23), * commit v3.0.0-rc1~154^2~1 (Help: Add notes about relocatability of config-file packages, 2014-01-07), and * commit v3.2.0-rc1~345^2 (Help: Warn that paths should not be used in INTERFACE_ build properties, 2014-11-22). These commits broke the natural flow of the original manual and made wording after the new content make less sense. Move the content into new subsections to restore the flow of the original manual and to make explicitly the purpose of the new content. Shorten the relocatable usage requirement "warnings". Refer to the new cmake-packages(7) manual subsection to reduce duplication. Also clarify the distinction between paths to library dependencies and paths to their header files.
| * Help: Fix typo in cmake-packages(7) manualBrad King2015-04-031-1/+1
| | | | | | | | relevnt => relevant
| * Help: Fix syntax in non-relocatable usage requirements exampleBrad King2015-04-031-4/+4
| | | | | | | | | | The example in cmake-packages(7) is meant to be incorrect for use of absolute paths, not for its syntax.
* | Help: Split cmake-generators(7) into linkable subsectionsBrad King2015-04-031-1/+25
| | | | | | | | | | | | | | Many places in our documentation refer to "Makefile Generators" or "Visual Studio" generators as a group of generators. Give such places a linkable document section to reference since they cannot cross-reference the individual generators in the groups.
* | Merge topic 'remove-DEFINITIONS-directory-property'Brad King2015-04-021-0/+1
|\ \ | | | | | | | | | | | | 06f61c26 Do not treat DEFINITIONS as a built-in directory property
| * | Do not treat DEFINITIONS as a built-in directory propertyStephen Kelly2015-04-021-0/+1
| |/ | | | | | | | | | | | | | | Add policy CMP0059 to cover this change. The property has been deprecated since CMake 2.4 anyway. This will help clean up cmMakefile -- the DefineFlagsOrig member should not need to exist.
* | Help: Document conversion of PATH/FILEPATH cache values to absolute pathsBrad King2015-04-011-1/+9
| | | | | | | | Suggested-by: Roger Leigh <rleigh@codelibre.net>
* | Help: Add link target to cmake-language.7 variables sectionBrad King2015-04-011-0/+2
|/
* Help: Add link target to cmake-language.7 lists sectionBrad King2015-03-311-0/+2
|
* Merge topic 'ninja-require-byproducts'Brad King2015-03-231-0/+1
|\ | | | | | | | | | | | | | | bd9c7f9b Ninja: Add policy to require explicit custom command byproducts ed8e30b0 cmGlobalNinjaGenerator: Optimize handling of known build outputs ad094f43 cmGlobalNinjaGenerator: Fix spelling of "unknown" 82a37d3c cmGlobalNinjaGenerator: Drop unused member
| * Ninja: Add policy to require explicit custom command byproductsBrad King2015-03-201-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Add policy CMP0058 to avoid generating 'phony' ninja rules for unknown custom command dependencies. This requires projects to specify their custom command byproducts explicitly. With this requirement we no longer have to assume that unknown custom command dependencies are generated and can instead simply assume they are source files expected to exist when the build starts. This is particularly important in in-source builds. It is also helpful for out-of-source builds to allow Ninja to diagnose missing files before running custom command rules that depend on them.
* | Merge topic 'add-extra-qbs-generator'Brad King2015-03-231-0/+1
|\ \ | | | | | | | | | | | | f85db2f3 Qbs: Add new 'extra' generator for qbs project files
| * | Qbs: Add new 'extra' generator for qbs project filesStanislav Ionascu2015-03-201-0/+1
| |/
* | Merge topic 'xcode-xctest'Brad King2015-03-232-0/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 4178cd88 Help: Add notes for topic 'xcode-xctest' 87a4b858 Tests: Add XCTest example to test Frameworks and Cocoa App Bundles ba14510b OS X: Add FindXCTest module 3714955b OS X: Add handling for XCTest bundles 54a5cdbb Tests: Compute Xcode version for any generator on OS X
| * | OS X: Add FindXCTest moduleGregor Jasny2015-03-231-0/+1
| | | | | | | | | | | | | | | | | | | | | Add a module to lookup XCTest Framework and xctest utility. It also provides APIs for creating 'xctest' targets. Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
| * | OS X: Add handling for XCTest bundlesGregor Jasny2015-03-231-0/+1
| |/ | | | | | | | | | | | | | | | | | | 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>
* | Merge topic 'ctest-repeat-until-fail'Brad King2015-03-231-0/+5
|\ \ | |/ |/| | | | | | | 6bce0276 Help: Add notes for topic 'ctest-repeat-until-fail' fde70a1b ctest: Add a new --repeat-until-fail option
| * ctest: Add a new --repeat-until-fail optionBill Hoffman2015-03-231-0/+5
| | | | | | | | | | This option tells ctest to run each test N times until the test fails or the N times have run. This is useful for finding random failing tests.
* | Merge topic 'refactor-cmGeneratorExpression'Brad King2015-03-121-4/+4
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | ec428faf Genex: Extend cmGeneratorExpressionContext constructor. 082b6a9d Genex: Split cmGeneratorExpressionContext into own file. 9df1f0fc Genex: Split cmGeneratorExpressionNode into own file. 80b9f0cb Genex: Extract an evaluateWithContext method. 642048ce Help: Move docs of $<0:...> and $<1:...> to output section.
| * | Help: Move docs of $<0:...> and $<1:...> to output section.Stephen Kelly2015-03-101-4/+4
| | | | | | | | | | | | | | | These are not 'logical' expressions. They create output and are often used together with the logical expressions.
* | | Merge topic 'main_dependency_diagnostic'Brad King2015-03-121-0/+1
|\ \ \ | |/ / |/| | | | | | | | 242c3966 add_custom_command: Diagnose MAIN_DEPENDENCY limitation.
| * | add_custom_command: Diagnose MAIN_DEPENDENCY limitation.Nils Gladitz2015-03-091-0/+1
| |/ | | | | | | | | The new policy CMP0057 diagnoses reuse of the same MAIN_DEPENDENCY across multiple custom commands.
* | Genex: Allow COMPILE_LANGUAGE when processing include directories.Stephen Kelly2015-03-091-1/+5
| | | | | | | | Issue an error if this is encountered by an IDE generator.
* | Genex: Allow COMPILE_LANGUAGE when processing compile definitions.Stephen Kelly2015-03-091-0/+10
| | | | | | | | Issue an error if this is encountered by an IDE generator.
* | Genex: Enable use of COMPILE_LANGUAGE for compile options.Stephen Kelly2015-03-091-0/+30
|/ | | | | | Follow-ups will allow the use of the generator expression for compile definitions and include directories for non-IDE generators.
* Merge topic 'wix-shortcut-properties'Brad King2015-02-231-0/+3
|\ | | | | | | | | | | | | | | | | | | 6cc01c14 CPackWIX: Add release notes for the wix-shortcut-properties topic. 135febf0 CPackWIX: Enhance CMake CPack WIX generated installer. e6731f48 CPackWIX: Add new CPACK_STARTUP_SHORTCUTS property. 279605f5 CPackWIX: Add installed file properties for the creation of shortcuts. 53d7daff CPackWIX: Refactor start menu and desktop shortcut creation. dc0f3fb4 CPackWIX: Explicitly list CPack WIX headers for IDE convenience.
| * CPackWIX: Add new CPACK_STARTUP_SHORTCUTS property.Nils Gladitz2015-02-211-0/+1
| |
| * CPackWIX: Add installed file properties for the creation of shortcuts.Nils Gladitz2015-02-211-0/+2
| |
* | Merge topic 'private-FindJsonCpp'Brad King2015-02-231-1/+0
|\ \ | |/ |/| | | | | | | a41d621d bootstrap: Add --(no-)system-jsoncpp options a5768442 FindJsonCpp: Drop new module due to upstream jsoncpp providing package
| * FindJsonCpp: Drop new module due to upstream jsoncpp providing packageBrad King2015-02-201-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Since jsoncpp 0.7.0 (2014-11-20) the upstream may provide a CMake package configuration file such that find_package(jsoncpp) will find a jsoncppConfig.cmake file. In order to avoid conflicting with this (especially on case-insensitive filesystems), and since we always prefer projects to provide package config files (that they maintain), it is better to not provide FindJsonCpp publicly. Move FindJsonCpp into a private source directory that is not installed so that we can still use it for building CMake itself. Reported-by: Ryan Pavlik <ryan.pavlik@gmail.com>
* | cmTarget: Remove template argument workaround.Stephen Kelly2015-02-171-28/+0
| | | | | | | | | | | | Pre-C++98 compilers required that the template argument be used in the function parameters. Those compilers are no longer supported as hosts, so drop the workaround.
* | CheckFortranCompilerFlag: Add module to check Fortran flag existenceNicolas Bock2015-02-051-0/+1
|/ | | | | | Copy the CheckCCompilerFlag module and replace 'C' with 'Fortran'. Also update the common patterns module to match some Fortran compiler messages.
* Merge topic 'doc-3.2-relnotes'Brad King2015-02-051-0/+2
|\ | | | | | | | | | | | | | | | | d81bbc3f Help: Add 3.2 release note for AUTORCC dependency tracking 0f38d9c2 Help: Add 3.2 release notes for file(GENERATE) features 0f580e8e Help: Organize and revise 3.2 release notes e08a78dc Help: Consolidate 3.2 release notes 3a4381b6 Help: Add link target to cmake-language.7 encoding section
| * Help: Add link target to cmake-language.7 encoding sectionBrad King2015-02-051-0/+2
| |
* | Help: Add some cross-linking.Stephen Kelly2015-02-041-1/+1
|/
* Features: Define meaning for no language standard defaultBrad King2015-01-291-1/+3
| | | | | | | | | | | | 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.
* VS: Add source file property to set extra hlsl shader flagsRobert Goulet2015-01-281-0/+1
| | | | | Create a VS_SHADER_FLAGS source file property so that we can set all other Visual Studio .hlsl shader file compilation flags.
generated by cgit v0.12 at 2025-03-24 04:02:42 (GMT)