mirror of
https://github.com/Kitware/CMake.git
synced 2026-08-13 17:07:57 +00:00
277c12a4c7
Try to be a bit more consistent about: - Placing angle brackets around text which serves as a placeholder rather than being literal. - Using curly brackets rather than angle brackets to denote groups where one of the options is required. - Describing optional list arguments like `<x>...` rather than `[<x>...]`. (Instances of lists not associated with keywords are intentionally left as-is, however.) Also, teach our CMake lexer to understand curly braces used as above (prior uses were only in parsed literals without syntax highlighting), and to highlight them (and remaining uses of angle braces) as the type Punctuation rather than the type Operator, for consistency with square braces.
13 lines
448 B
ReStructuredText
13 lines
448 B
ReStructuredText
The default search order is designed to be most-specific to
|
|
least-specific for common use cases.
|
|
Projects may override the order by simply calling the command
|
|
multiple times and using the ``NO_*`` options:
|
|
|
|
.. parsed-literal::
|
|
|
|
|FIND_XXX| (|FIND_ARGS_XXX| PATHS <paths>... NO_DEFAULT_PATH)
|
|
|FIND_XXX| (|FIND_ARGS_XXX|)
|
|
|
|
Once one of the calls succeeds the result variable will be set
|
|
and stored in the cache so that no call will search again.
|