From 37edafef74ca5e3e69944056c934497413b21b9c Mon Sep 17 00:00:00 2001 From: Lars Melchior Date: Tue, 14 Apr 2020 15:44:30 +0200 Subject: [PATCH] wording --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 19bc936..9bf8815 100644 --- a/README.md +++ b/README.md @@ -88,7 +88,7 @@ See [Format.cmake](https://github.com/TheLartians/Format.cmake) for more options - You recommend to add external dependencies using CPM.cmake. Will this force users of my library to use CPM as well? - [CPM.cmake](https://github.com/TheLartians/CPM.cmake) should be invisible for your library users as it's a self-contained CMake Script. + [CPM.cmake](https://github.com/TheLartians/CPM.cmake) should be invisible to library users as it's a self-contained CMake Script. If problems do arise, users can always opt-out by defining `CPM_USE_LOCAL_PACKAGES`, which will override all calls to `CPMAddPackage` with `find_package`. Alternatively, you could use `CPMFindPackage` instead of `CPMAddPackage`, which will try to use `find_package` before calling `CPMAddPackage` as a fallback. Both approaches should be compatible with common C++ package managers without modifications, however come with the cost of reproducible builds.