Hello! You may try to perform some kind of "caching" actions yourself: store a checksum for the downloaded dependency archive and only build it if its checksum changes or the dependency with this checksum hasn't been already built. You may only store the checksum for the archive download link if it is possible to guarantee that the link is different for different versions of the dependency.
Here <https://gitlab.com/UtilityToolKit/utk.cmake/blob/master/utk_cmake_package.cmake#L76> you may find an ugly implementation of a similar logic. Best regards, Innokentiy -- Sent from: http://cmake.3232098.n2.nabble.com/ -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
