This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 83badd91bff023b60c40a09a6761957ab50cfc90 (commit)
via 3c8dab73cb01285da589b033b31b76623a74520c (commit)
via 23752d5bad631e7948796281f3c7548bbec80fd4 (commit)
via ad024439f50f79f76b10b31f1c1a3e5f73f09462 (commit)
from 0fb4e0ad15540e782b4baa7117e8db30c8afe640 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=83badd91bff023b60c40a09a6761957ab50cfc90
commit 83badd91bff023b60c40a09a6761957ab50cfc90
Merge: 3c8dab73cb 23752d5bad
Author: Craig Scott
AuthorDate: Sun Nov 3 22:40:23 2019 +
Commit: Kitware Robot
CommitDate: Sun Nov 3 17:40:32 2019 -0500
Merge topic 'docs-file-GET_RUNTIME_DEPENDENCIES'
23752d5bad Help: Typo and grammar fixes for file(GET_RUNTIME_DEPENDENCIES)
Acked-by: Kitware Robot
Merge-request: !3982
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3c8dab73cb01285da589b033b31b76623a74520c
commit 3c8dab73cb01285da589b033b31b76623a74520c
Merge: 0fb4e0ad15 ad024439f5
Author: Craig Scott
AuthorDate: Sun Nov 3 22:35:07 2019 +
Commit: Kitware Robot
CommitDate: Sun Nov 3 17:35:16 2019 -0500
Merge topic 'docs-list-remove_item'
ad024439f5 Help: list(REMOVE_ITEM) removes all instances, not just the
first found
Acked-by: Kitware Robot
Merge-request: !3977
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=23752d5bad631e7948796281f3c7548bbec80fd4
commit 23752d5bad631e7948796281f3c7548bbec80fd4
Author: Craig Scott
AuthorDate: Sun Nov 3 22:44:36 2019 +1100
Commit: Craig Scott
CommitDate: Sun Nov 3 22:44:36 2019 +1100
Help: Typo and grammar fixes for file(GET_RUNTIME_DEPENDENCIES)
Note that ``MODULE`` s was rendering strangely, so the wording
has been tweaked to avoid needing to specify ``MODULE`` as a
plural word. Modules are still libraries, so it is okay to call them as
such where it doesn't cause any ambiguity.
diff --git a/Help/command/file.rst b/Help/command/file.rst
index 83e451636f..b186177eb6 100644
--- a/Help/command/file.rst
+++ b/Help/command/file.rst
@@ -187,14 +187,14 @@ The arguments are as follows:
are typically created with :command:`add_executable`, but they do not have to
be created by CMake. On Apple platforms, the paths to these files determine
the value of ``@executable_path`` when recursively resolving the libraries.
- Specifying ``STATIC`` libraries, ``MODULE`` s, or ``SHARED`` libraries here
+ Specifying any kind of library (``STATIC``, ``MODULE``, or ``SHARED``) here
will result in undefined behavior.
``LIBRARIES ``
List of library files to read for dependencies. These are libraries that are
typically created with :command:`add_library(SHARED)`, but they do not have
- to be created by CMake. Specifying ``STATIC`` libraries, ``MODULE`` s, or
- executables here will result in undefined behavior.
+ to be created by CMake. Specifying ``STATIC`` libraries, ``MODULE``
+ libraries, or executables here will result in undefined behavior.
``MODULES ``
List of loadable module files to read for dependencies. These are modules
@@ -209,13 +209,13 @@ The arguments are as follows:
platforms, these directories are searched if the dependency is not found in
any of the other usual paths. If it is found in such a directory, a warning
is issued, because it means that the file is incomplete (it does not list all
- of the directories that contain its dependencies.) On Windows platforms,
+ of the directories that contain its dependencies). On Windows platforms,
these directories are searched if the dependency is not found in any of the
other search paths, but no warning is issued, because searching other paths
is a normal part of Windows dependency resolution. On Apple platforms, this
argument has no effect.
-``BUNDLE_EXECTUBLE ``
+``BUNDLE_EXECUTABLE ``
Executable to treat as the "bundle executable" when resolving libraries. On
Apple platforms, this argument determines the value of ``@executable_path``
when recursively resolving libraries for ``LIBRARIES`` and ``MODULES`` files.
@@ -284,7 +284,7 @@ On Linux platforms, library resolution works as follows:
dependency is resolved to that file. In this case, a warning is issued,
because finding a file in one of the ``DIRECTORIES`` means that the
depending file is not complete (it does not list all the directories from
- which it pulls dependencies.)
+ which it pulls dependencies).
5. Otherwise, the dependency is unresolved.
On Windows platforms, library resolution works as fo
