summaryrefslogtreecommitdiffstats
path: root/Help
Commit message (Collapse)AuthorAgeFilesLines
* VS: Provide the default platform name to project codeBrad King2019-04-195-2/+26
| | | | | | | | | | | | | | | | | | The value of `CMAKE_VS_PLATFORM_NAME` is computed by Visual Studio generators based on `CMAKE_GENERATOR_PLATFORM` or some default. Prior to the VS 2019 generator, the default was always `Win32`. However, for the `Visual Studio 16 2019` generator, the default is based on the host platform. Store the default in a new `CMAKE_VS_PLATFORM_NAME_DEFAULT` variable for use by project code. This is particularly useful in toolchain files because they are allowed to set `CMAKE_GENERATOR_PLATFORM` and so `CMAKE_VS_PLATFORM_NAME` is not yet known. Of course the toolchain file author knows whether it will set `CMAKE_GENERATOR_PLATFORM`, and if not then `CMAKE_VS_PLATFORM_NAME_DEFAULT` provides the platform name that will be used. Fixes: #19177
* Merge branch 'FindFontconfig-var-case' into release-3.14Brad King2019-03-271-0/+14
|\ | | | | | | Merge-request: !3153
| * FindFontconfig: Convert module variables to camel caseBrad King2019-03-261-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Our documented standard for find module variable names is to match the case of the find module package name. This was overlooked when the module was added by commit 84e7920b3a (FindFontconfig: Add module to find Fontconfig, 2018-09-27, v3.14.0-rc1~523^2). The module was released with the upper case names in CMake 3.14.0, so fix it to have camel case names in 3.14.1. This is incompatible but anyone using a given release series should be using the latest patch on it and we've made breaking fixups on newly released features like this before. Reported-by: Christophe Giboudeaux <christophe@krop.fr> Fixes: #19094
* | Help: Clarify policy CMP0082 documentationBrad King2019-03-211-3/+5
|/ | | | | | | The policy documentation added by commit fc8955e889 (add_subdirectory: Run subdirectory install rules in correct order, 2018-10-02, v3.14.0-rc1~565^2~1) left out our usual sentence about the policy providing compatibility.
* Merge branch 'docs-xcode-schemes' into release-3.14Brad King2019-03-063-34/+29
|\ | | | | | | Merge-request: !3066
| * Help: Remove note that Xcode scheme generator is experimentalCraig Scott2019-03-061-5/+0
| |
| * Help: Trivial typo fix for CMAKE_XCODE_GENERATE_SCHEMECraig Scott2019-03-061-1/+1
| |
| * Help: Sort lists of (CMAKE_)XCODE_SCHEME_... variables and propertiesCraig Scott2019-03-063-28/+28
| |
* | Merge branch 'docs-install-destinations' into release-3.14Brad King2019-03-051-51/+85
|\ \ | | | | | | | | | Merge-request: !3052
| * | Help: clarify DESTINATION and TYPE usage for install()Craig Scott2019-03-051-51/+85
| |/
* | Merge branch 'ios-docs' into release-3.14Brad King2019-03-052-1/+62
|\ \ | | | | | | | | | Merge-request: !3047
| * | Help: CMAKE_MACOSX_BUNDLE is ON for iOS/tvOS/watchOSRuslan Baratov2019-03-051-0/+3
| | |
| * | Help: Example of tweaking iOS/tvOS/watchOS buildRuslan Baratov2019-03-051-0/+48
| | | | | | | | | | | | | | | CMAKE_OSX_ARCHITECTURES and CMAKE_OSX_DEPLOYMENT_TARGET variables can be used to tweak iOS/tvOS/watchOS build
| * | Help: find_package with fat iOS librariesRuslan Baratov2019-03-051-1/+11
| |/
* | iOS: Add IOS variableRuslan Baratov2019-03-052-0/+5
|/ | | | | | | Since commit 11da882a12 (Apple: Introduce separate system name for iOS, tvOS, and watchOS, 2018-01-15, v3.14.0-rc1~14^2~1) we support setting `CMAKE_SYSTEM_NAME` to `iOS`. Existing iOS toolchain files already set `IOS` as a short-hand variable, so do the same here.
* Merge branch 'vs2019' into release-3.14Brad King2019-02-281-1/+1
|\ | | | | | | Merge-request: !3044
| * Help: Update VS 2019 generator release note for preview 4Brad King2019-02-281-1/+1
| |
* | Merge branch 'docs-rpath-origin-apple' into release-3.14Brad King2019-02-271-7/+7
|\ \ | | | | | | | | | Merge-request: !3020
| * | Help: Fix minor inaccuracies of what BUILD_RPATH_USE_ORIGIN affectsCraig Scott2019-02-271-7/+7
| |/
* | Merge branch 'FindOctave-remove' into release-3.14Brad King2019-02-273-4/+0
|\ \ | | | | | | | | | Merge-request: !3027
| * | FindOctave: Remove module pending further workBrad King2019-02-263-4/+0
| |/ | | | | | | | | | | | | | | | | | | | | The `FindOctave` module added by commit 170bcb6fdc (FindOctave: Add module to find GNU octave, 2018-11-17, v3.14.0-rc1~283^2) has a few problems in its implementation that need to be worked out before the module can be included in a CMake release. These were missed during review. Remove the module for now. It can be restored later with a fresh review. Issue: #18991
* | Merge branch 'doc-ctest-build-and-test-summary' into release-3.14Brad King2019-02-261-2/+3
|\ \ | | | | | | | | | Merge-request: !3017
| * | Help: Fix --build-and-test synopsis in ctest(1)Paul Seyfert2019-02-261-2/+3
| |/ | | | | | | | | | | The synopsis added by commit 9d3aa95ca4 (Help: Divide ctest(1) manual options into sections, 2017-11-08, v3.11.0-rc1~359^2~2) is missing the actual `--build-and-test` argument! Add it now.
* | Merge branch 'releasenotes_arch_independent' into release-3.14Brad King2019-02-251-0/+5
|\ \ | | | | | | | | | Merge-request: !3012
| * | Help: Add release note for new ARCH_INDEPENDENT optionCraig Scott2019-02-241-0/+5
| |/
* | Merge branch 'docs_try_commands' into release-3.14Brad King2019-02-252-25/+33
|\ \ | | | | | | | | | Merge-request: !3013
| * | Help: Caveat for try_compile() and CMAKE_TRY_COMPILE_PLATFORM_VARIABLESCraig Scott2019-02-241-1/+3
| | |
| * | Help: Consistency in try_compile() docs for target typeCraig Scott2019-02-241-8/+14
| | |
| * | Help: try_compile() readability and grammar improvementsCraig Scott2019-02-241-6/+6
| | |
| * | Help: User-provided variable names for try_* commandsCraig Scott2019-02-242-12/+12
| |/ | | | | | | | | All uppercase is typically used for command keywords. Non-keyword arguments should generally be shown as `<something>` according to the CMake documentation guide.
* | Merge branch 'remove-exclude-from-all-warning' into release-3.14Brad King2019-02-222-2/+14
|\ \ | | | | | | | | | Merge-request: !3002
| * | EXCLUDE_FROM_ALL: Don't warn if installing target excluded from allCraig Scott2019-02-212-2/+14
| |/ | | | | | | | | | | | | | | | | The original warning pre-dates support for install components. There are now legitimate scenarios where an install(TARGETS) command may list a target that is excluded from all, e.g. hierarchical projects that will never install the component such a target belongs to. Fixes: #18938
* | Merge branch 'link-options' into release-3.14Brad King2019-02-201-3/+4
|\ \ | | | | | | | | | Merge-request: !2996
| * | PIE link options: No warning when policy CMP0083 is not set.Marc Chevrier2019-02-201-3/+4
| |/ | | | | | | Fixes: #18955
* | Merge branch 'fix-implicit-includes-fortran' into release-3.14Brad King2019-02-201-1/+6
|\ \ | | | | | | | | | Merge-request: !2994
| * | Fortran: Do not suppress explicit use of implicit include directoriesBrad King2019-02-201-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit 2e91627dea (ParseImplicitIncludeInfo: add Fortran implicit include handling, 2019-01-25, v3.14.0-rc1~73^2) we actually populate `CMAKE_Fortran_IMPLICIT_INCLUDE_DIRECTORIES` for the first time. This value may be useful to project code to pass to other tooling that wants to preprocess the way Fortran does, so we should compute the value. However, compilers like `gfortran` do not actually search their own implicit include directories for `.mod` files. The directories must be passed via `-I` in order for `.mod` files in them to be found. Since Fortran has no standard library header files that we need to avoid overriding, it is safe to *not* filter out implicit include directories from those passed explicitly via `-I` options. Skip this filtering so that include directories specified by project code to find `.mod` files will be searched by the compiler even if they happen to be implicitly searched by the preprocessor. Fixes: #18914
* | | Merge branch 'file_symlink_docs' into release-3.14Brad King2019-02-181-23/+23
|\ \ \ | | | | | | | | | | | | Merge-request: !2974
| * | | Help: Clarify and improve readability of link-related file subcommandsCraig Scott2019-02-161-23/+23
| | |/ | |/|
* | | Merge branch 'externalproject_docs' into release-3.14Brad King2019-02-181-1/+1
|\ \ \ | | | | | | | | | | | | Merge-request: !2978
| * | | Release notes: Make ExternalProject dot points consistentCraig Scott2019-02-171-1/+1
| |/ / | | | | | | Use same phrasing and command linking.
* | | Help: Remove outdated statement about get_filename_component()Craig Scott2019-02-161-4/+3
|/ / | | | | | | | | | | | | | | After !2853, the statement that the "longest file extension is always considered" is no longer true. Both NAME_WLE and LAST_EXT now return details based on the shortest file extension. Fixes: 7a25ef326b (Help: Add documentation for new get_filename_component components, 2019-01-24, 3.14.0-rc1)
* | Merge branch 'doc-if-legacy' into release-3.14Brad King2019-02-111-1/+1
|\ \ | | | | | | | | | Merge-request: !2950
| * | Help: Fix elseif/endif typoJuuso "Linda" Lapinlampi2019-02-111-1/+1
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In CMake 3.13.x, we had this evaluation for if() conditions: if(a) elseif(b) else(a) endif(a) The sensible intention of the change in commit c2efb3efcd (Help: Revise docs on Scripting Commands, 2018-10-16, v3.14.0-rc1~505^2) was: > "endif", "endfunction" etc: Explain that the argument is optional and > maintained for compatibility only Instead of "endif", it ended up being written to the documentation as "elseif" by the commit author (oops) to if()'s page. if(a) elseif(a!?) else() endif(a?) Truthfully, endif()'s parameter should be an optional verbatim repeat and not elseif()'s. If it wasn't, elseif() would be described to be the same as if(). The rightful intended description is: if(a) elseif(b) else() endif() Fix that typo.
* | Merge branch 'ghs-relnotes' into release-3.14Brad King2019-02-111-0/+28
|\ \ | | | | | | | | | Merge-request: !2934
| * | Help: Update 3.14 release notes for GHS changesFred Baksik2019-02-111-0/+28
| | |
* | | Merge branch 'ghs-updates' into release-3.14Brad King2019-02-085-0/+22
|\ \ \ | |/ / | | | | | | Merge-request: !2943
| * | GHS: Document usage of GHS_NO_SOURCE_GROUP_FILEFred Baksik2019-02-085-0/+22
| | | | | | | | | | | | -- Also change variable name to CMAKE_GHS_NO_SOURCE_GROUP_FILE
* | | Help: Add notes for `file(CREATE_LINK)` subcommandTushar Maheshwari2019-02-081-0/+3
|/ /
* | Merge branch 'doc-object-library-link' into release-3.14Brad King2019-02-071-2/+2
|\ \ | | | | | | | | | Merge-request: !2933
| * | Help: Clarify 3.14 release note about object library dependenciesBrad King2019-02-071-2/+2
| |/ | | | | | | | | Revise the note from commit bab24e782c (target_link_libraries: Propagate dependencies of object libraries, 2018-12-10, v3.14.0-rc1~260^2).
generated by cgit v0.12 at 2025-01-14 14:09:10 (GMT)