Is there anyway to speed-up "configure" step with CPM? about cpm.cmake HOT 5 CLOSED

Hm I don't think it's possible for CMake to "cache" a subdirectory, as it needs to run all dependency's CMakeLists to ensure that all contained targets and functions etc are defined and in the correct order.
One thing you could do is to pre-build and install the dependency "normally" and then use CPMFindPackage instead of CPMAddPackage too add it. That way CPM should pick up the installed version and will use the pre-built libraries and headers (assuming the CMake Module path is set up correctly).
Another way to speed up configure time is setting a generator such as ninja, which is noticeably faster than make in configuration and build times.

from cpm.cmake.

Thanks, good suggestion, I'll try precompiling and use CPMFindPackage. I thought you added an option for CPMAddPackage to prefer to find_package first, is this correct?

from cpm.cmake.

Yeah, you could also get this behaviour globally for CPMAddPackage by defining CPM_USE_LOCAL_PACKAGES=1 as a CMake option or environmental variable.

from cpm.cmake.

Closing as there is nothing that CPM can really do against slow dependency configure times.
Did installing and CPMFindPackage work for you?

from cpm.cmake.

As it turns out the largest bottleneck for us was CMake's FetchContent doing essentially nothing. Therefore the most recent release bypasses FetchContent for previously cached dependencies. For us this reduced configuration time from minutes to seconds. @bolu-atx perhaps you could try updating CPM.cmake to at least 0.28.0 and see if it reduces configuration time for your projects as well.

from cpm.cmake.