DOWNLOAD_ONLY not parsed? about cpm.cmake

[JohelEGP]

It does solve it.

[JohelEGP]

Here's JEGPFindDependencies.cmake: https://github.com/johelegp/jegp/blob/dd9e15ee4d5ec3e233d252fca091ee638777a8ce/cmake/JEGPFindDependencies.cmake.
And NEWLIBFindDependencies.cmake:

if(NOT EXISTS ${CMAKE_CURRENT_LIST_DIR}/CPM.cmake)
    message(STATUS "Downloading CPM.cmake")
    file(DOWNLOAD
         https://github.com/TheLartians/CPM.cmake/raw/master/cmake/CPM.cmake
         ${CMAKE_CURRENT_LIST_DIR}/CPM.cmake)
endif()

include(CPM)

find_package(SFML 2.5 REQUIRED COMPONENTS graphics)
CPMFindPackage(
    NAME jegp_cmake_modules
    GITHUB_REPOSITORY johelegp/jegp.cmake_modules
    GIT_TAG master
    GIT_SHALLOW True)
CPMFindPackage(
    NAME jegp
    GIT_REPOSITORY /mnt/sda5/documents/c++/repositories/jegp/jegp
    GIT_TAG master
    GIT_SHALLOW True)
CPMFindPackage(
    NAME range-v3
    GITHUB_REPOSITORY ericniebler/range-v3
    GIT_TAG master
    GIT_SHALLOW True
    DOWNLOAD_ONLY True)
if(range-v3_ADDED)
    add_library(range-v3::range-v3 INTERFACE IMPORTED GLOBAL)
    target_include_directories(range-v3::range-v3
                               INTERFACE ${range-v3_SOURCE_DIR}/include)
endif()
CPMFindPackage(
    NAME fmt
    GITHUB_REPOSITORY fmtlib/fmt
    GIT_TAG master
    GIT_SHALLOW True)
CPMFindPackage(
    NAME mp-units
    GITHUB_REPOSITORY mpusz/units
    GIT_TAG master
    GIT_SHALLOW True
    DOWNLOAD_ONLY True)

list(APPEND CMAKE_MODULE_PATH ${jegp_cmake_modules_SOURCE_DIR})

if(mp-units_ADDED)
    add_subdirectory(${mp-units_SOURCE_DIR}/src ${mp-units_BINARY_DIR})
endif()

The dependency story of jegp_cmake_modules is the same as that of range-v3, but the former works. The only difference is that range-v3 is declared as DOWNLOAD_ONLY True.

[TheLartians]

Hey thanks for the report! I think the problem was that we were incorrectly trying to download the package when we should have only been checking its availability. I've corrected that in #120. Could you test if the patched version solves the issue for you?

[TheLartians]

Great, thanks for verifying it! The fix is now published in version 0.24.