Olivier Le Doeuff

You shouldn't use `include_directories` in modern cmake but rather create a target and use `target_include_directories` Did you took a look at [boost-cmake](https://github.com/Orphis/boost-cmake) ?

I've made this to use standalone asio: [asio.cmake](https://github.com/OlivierLDff/asio.cmake) ```cmake set(ASIO_REPOSITORY "https://github.com/chriskohlhoff/asio" CACHE STRING "Repository of asio" ) set(ASIO_TAG "asio-1-18-2" CACHE STRING "Git tag of asio" ) set(ASIOCMAKE_REPOSITORY "https://github.com/OlivierLDff/asio.cmake" CACHE STRING...

Is there any guidelines for unit test? Should it be tested with real package?

For opencv, I created a fork of my own and I explain step here to get it to play nicely with CPM https://github.com/opencv/opencv/issues/20548#issuecomment-907873313 I opened this issue for opencv too,...

From experience I wouldn't recommand using git branch, because then it's hard to track in the life of the project which dependency is expected where. Also, if a branch name...

I believe you should use something like: ``` git config --global url."https://olivierldff:[email protected]".insteadOf "https://github.com" ``` And only keep the url without the token in your source cmakelists file. Syntax is what...

Maybe it should be highlighted as a cool trick in readme, I discovered this technique from some of your comments but it is not mentioned a lot on the internet.

Does this create a copy?

Ok so a git clone is happening that was my question

It's really cool to have common library as part of unit testing. Because it test real world scenario. Complexity and hidden bugs often hides in there.