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 <craig.sc...@crascit.com> AuthorDate: Sun Nov 3 22:40:23 2019 +0000 Commit: Kitware Robot <kwro...@kitware.com> 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 <kwro...@kitware.com> Merge-request: !3982 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3c8dab73cb01285da589b033b31b76623a74520c commit 3c8dab73cb01285da589b033b31b76623a74520c Merge: 0fb4e0ad15 ad024439f5 Author: Craig Scott <craig.sc...@crascit.com> AuthorDate: Sun Nov 3 22:35:07 2019 +0000 Commit: Kitware Robot <kwro...@kitware.com> 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 <kwro...@kitware.com> Merge-request: !3977 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=23752d5bad631e7948796281f3c7548bbec80fd4 commit 23752d5bad631e7948796281f3c7548bbec80fd4 Author: Craig Scott <craig.sc...@crascit.com> AuthorDate: Sun Nov 3 22:44:36 2019 +1100 Commit: Craig Scott <craig.sc...@crascit.com> 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 <library_files>`` 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 <module_files>`` 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_file>`` +``BUNDLE_EXECUTABLE <bundle_executable_file>`` 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 follows: @@ -331,8 +331,8 @@ On Windows platforms, library resolution works as follows: dependency is resolved to that file. 5. Otherwise, if the library exists in one of the directories specified by ``DIRECTORIES``, in the order they are listed, the dependency is resolved to - that file. (In this case, a warning is not issued, because searching other - directories is a normal part of Windows library resolution.) + that file. In this case, a warning is not issued, because searching other + directories is a normal part of Windows library resolution. 6. Otherwise, the dependency is unresolved. On Apple platforms, library resolution works as follows: @@ -350,9 +350,9 @@ On Apple platforms, library resolution works as follows: existing file, the dependency is resolved to that file. 4. Otherwise, if the dependency starts with ``@rpath/``, and replacing ``@rpath/`` with one of the ``RPATH`` entries of the depending file yields - an existing file, the dependency is resolved to that file. (Note that + an existing file, the dependency is resolved to that file. Note that ``RPATH`` entries that start with ``@executable_path/`` or ``@loader_path/`` - also have these items replaced with the appropriate path.) + also have these items replaced with the appropriate path. 5. Otherwise, if the dependency is an absolute file that exists, the dependency is resolved to that file. 6. Otherwise, the dependency is unresolved. https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ad024439f50f79f76b10b31f1c1a3e5f73f09462 commit ad024439f50f79f76b10b31f1c1a3e5f73f09462 Author: Craig Scott <craig.sc...@crascit.com> AuthorDate: Sat Nov 2 18:22:23 2019 +1100 Commit: Craig Scott <craig.sc...@crascit.com> CommitDate: Sat Nov 2 18:22:50 2019 +1100 Help: list(REMOVE_ITEM) removes all instances, not just the first found Fixes: #19908 diff --git a/Help/command/list.rst b/Help/command/list.rst index 39e7e2a69f..50bf417bf1 100644 --- a/Help/command/list.rst +++ b/Help/command/list.rst @@ -180,7 +180,7 @@ Insert elements to the 0th position in the list. list(REMOVE_ITEM <list> <value> [<value> ...]) -Removes the given items from the list. +Removes all instances of the given items from the list. .. _REMOVE_AT: ----------------------------------------------------------------------- Summary of changes: Help/command/file.rst | 20 ++++++++++---------- Help/command/list.rst | 2 +- 2 files changed, 11 insertions(+), 11 deletions(-) hooks/post-receive -- CMake _______________________________________________ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits