summaryrefslogtreecommitdiffstats
path: root/Help/command/find_package.rst
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'no-smiley'Brad King2018-10-291-1/+1
|\ | | | | | | | | | | | | 24fa04018c Help: Spell out ";-list" as "semicolon-separated list" Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2528
| * Help: Spell out ";-list" as "semicolon-separated list"Joachim Wuttke (o)2018-10-251-1/+1
| |
* | Help: Back-reference from find_package() to "Find Modules"Joachim Wuttke (o)2018-10-251-2/+3
|/ | | | viz., to section "Find Modules" in cmake-modules.7
* Help: Revise docs on Scripting CommandsJoachim Wuttke (l)2018-10-231-3/+7
| | | | | | | | | | | | | | | | | | | Revise docs for all "Scripting Commands", except four find_XXX that use a macro suite of their own. * Take full advantage of the improved syntax highlighting. * Make consequential use of <..> placeholders. * Clarify things here and there in the text. Specific improvements to some command docs: * "math": Correct description of novel hexadecimal capability. * "if", "foreach", "while": Provide link to "endif" etc * "foreach", "while": Mention "break" and "continue". * "foreach": Simplify explanation of ``RANGE`` and ``IN`` signatures; advise against negative arguments or reverse ranges (compare issue #18461) * "endif", "endfunction" etc: Explain that the argument is optional and maintained for compatibility only
* Help: Clarify find_package Module and Config mode relationJoachim Wuttke (l)2018-10-041-17/+17
|
* Help: Remove redundant recommendationBrad King2018-10-041-12/+4
| | | | | We suggest that users prefer the basic signature in two places. Drop the latter and move its related content to a better section.
* Help: Add internal section link to find_package command docsJoachim Wuttke (l)2018-10-041-6/+8
|
* Help: Add section headers to find_package commandJoachim Wuttke (l)2018-10-041-0/+15
| | | | | The document is pretty long but is already mostly organized into sections. Add explicit section headers.
* Help: Move find_package NO_POLICY_SCOPE to more appropriate locationJoachim Wuttke (l)2018-10-041-3/+3
|
* Help: Add table of contents to find_package command docsJoachim Wuttke (l)2018-10-041-0/+4
|
* Help: Rephrase summary in find_package command docsJoachim Wuttke (l)2018-10-041-1/+1
|
* Help: Replace occurrences of "Mac OS X" with "macOS"Bartosz Kosiorek2018-09-051-1/+1
| | | | | | | | Apple's main Operating system changed their name from OS X to macOS: https://www.engadget.com/2016/06/13/os-x-is-now-macos/ Revise documentation accordingly.
* doc: Consistently use <PackageName> for describing the name of a packageJean-Christophe Fillion-Robin2018-08-141-38/+38
|
* Help: Add explicit <PackageName>_ROOT variable documentationBrad King2018-07-201-2/+4
| | | | | | Add documentation for both the CMake variable and environment variable of this name pattern. Update references to these names to link to their documents. Clarify the pattern used to construct their names.
* Help: Add 'lib32|libx32|lib64' paths to find_package prefixesRuslan Baratov2018-03-211-9/+21
| | | | | Document the conditions when 'lib32|libx32|lib64' variants will be added to the list of possible installation prefixes.
* find_package: Use PackageName_ROOT variables as search prefixesBrad King2018-03-161-8/+16
| | | | | | | | | | | | | | | | | | | This feature was originally added by commit v3.9.0-rc1~71^2~2 (find_*: Add a new PackageRoot search path group, 2017-05-03) and documented by commit v3.9.0-rc1~71^2 (find_*: Add docs for PackageRoot search path group, 2017-05-03). However, we had to disable the feature and remove the documentation in commit v3.9.1~2^2 (find_*: Disable the PACKAGE_ROOT search path group for CMake 3.9, 2017-08-08) due to breaking projects that used `PackageName_ROOT` variables themselves. Add policy `CMP0074` to restore the `PackageName_ROOT` variable behavior in a compatible way. Also revise the stack of root paths to store the paths themselves rather than the package names. This way the policy can be considered at the `find_package` call site instead of individual `find_` calls inside a find module. Co-Author: Chuck Atkins <chuck.atkins@kitware.com> Issue: #17144
* Various typo fixesLuz Paz2018-01-031-1/+1
| | | | Some are user-facing. Others are source comments.
* find_*: Disable the PACKAGE_ROOT search path group for CMake 3.9Brad King2017-08-081-15/+8
| | | | | | | | | | | | | | | | Disable the feature added by commit v3.9.0-rc1~71^2~2 (find_*: Add a new PackageRoot search path group, 2017-05-03) and remove documentation added by commit v3.9.0-rc1~71^2 (find_*: Add docs for PackageRoot search path group, 2017-05-03). Unfortunately the name `<pkg>_ROOT` may already be set by projects for their own incompatible purposes. Disable the behavior change for now to fix the regression for CMake 3.9. We can restore it later with a policy. In order to keep the implementation and tests working, add an undocumented variable we can use in the tests to enable the behavior before the policy is introduced. Fixes: #17144
* find_*: Add docs for PackageRoot search path groupChuck Atkins2017-05-191-9/+16
|
* Help: Document find command search path separatorsBrad King2017-04-181-1/+4
| | | | | | | | The `find_*` commands read search paths from both CMake variables and from environment variables. Document how multiple values in these variables should be separated. Fixes: #16800
* find_package: Optionally sort globbed directories in a meaningful orderPierluigi Taddei2016-09-151-4/+14
| | | | | | | | | | | | Add `CMAKE_FIND_PACKAGE_SORT_{ORDER,DIRECTION}` variables to specify sort order and direction. When multiple package with the same name have been found in the same location sorting option can be used to force a specific version to be loaded (e.g. libA_1.12.0 instead of libA_1.1.0). Currently sorting by NAME and by NATURAL order have been implemented. Natural ordering makes use of the `strverscmp(3)` ordering.
* find_package: Extend search path for combined Windows/UNIX conventionSilvio Traversaro2016-08-241-0/+3
| | | | | | | | Find packages that install their cmake package configuration files in `lib/cmake/<name>` when they are installed in the default Windows CMAKE_INSTALL_PREFIX, `C:/Program Files/<name>`. Closes: #16212
* Help: Widen find_package search path tableSilvio Traversaro2016-08-231-7/+7
| | | | Make room for additional longer entries.
* Help: Document CMAKE_FIND_APPBUNDLE and CMAKE_FIND_FRAMEWORKBrad King2015-06-081-4/+3
| | | | | Add dedicated documents for these and link to them instead of duplicating their documentation in every find command.
* find_package: Drop search in recent cmake-gui locationsBrad King2015-05-081-11/+5
| | | | | | | | | | | | | | | | | | | | | | The find_package command, on Windows, has always searched build trees recently visited by cmake-gui (or CMakeSetup at one time). This was done when the command was created with the intention of simplifying workflows involving building multiple dependent projects. However, this behavior depends on recent developer interaction and therefore can create different find results based on transient system states. It can lead to surprising results and user confusion. Since this behavior was first added CMake has gained many more search options, better error messages when a package is not found, and a package registry. The latter in particular allows projects to make their build trees available for dependent projects to find without user intervention. Therefore the originally intended workflow can be achieved in other, more stable ways. After the above evoluion of find_package we have now decided that the magic search-where-cmake-gui-was behavior does more harm than good. Drop it. We do not need a policy for this behavior change because it only affects interactive use.
* find_package: Document CMAKE_FIND_PACKAGE_NAME variableGregor Jasny2015-01-111-0/+2
| | | | Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
* Allow the Package Registry to be disabled (#14849)Daniele E. Domenichelli2014-05-121-2/+6
| | | | | | | | | | | | | | | | When a project is packaged for redistribution the local package registries should not be updated or consulted. They are for developers. Add variables to disable use of package registries globally: * CMAKE_EXPORT_NO_PACKAGE_REGISTRY that disables the export(PACKAGE) command * CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY that disables the User Package Registry in all the find_package calls. * CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY that disables the System Package Registry in all the find_package calls. Update documentation and unit tests.
* Help: Mention in find_package that cmake-gui step is Windows-only (#14781)Brad King2014-03-031-0/+1
| | | | | | | Recently used cmake-gui locations are searched only on Windows because the Windows registry is used to record the values. This behavior is historical and may be removed by a policy in the future so rather than implementing it on other platforms simply document the current behavior.
* Help: Format find_package() command documentationBrad King2014-02-171-189/+171
| | | | | Add inline markup and explicit markup block syntax as needed. Add cross-references to other documentation as appropriate.
* Help: Document the CMAKE_FIND_ROOT_PATH* variables.Stephen Kelly2013-11-271-1/+1
| | | | | Add a replacement template for the variables, and link to them from the documentation for the find_* commands.
* Help: Factor out find_* command duplicationBrad King2013-10-161-52/+8
| | | | | | | These documents were represented in the builtin documentation using a common starting point with placeholders substituted by each command. Convert them back to this approach using the reStructuredText include directive and substitutions to avoid duplication.
* Convert builtin help to reStructuredText source filesKitware Robot2013-10-151-0/+406
Run the convert-help.bash script to convert documentation: ./convert-help.bash "/path/to/CMake-build/bin" Then remove it.