Right now, the range-v3 dependency causes errors when a project depends on fp and range-v3 like this:
--- stderr: core
CMake Error at /usr/lib/cmake/range-v3/range-v3-config.cmake:2 (add_library):
add_library cannot create imported target "range-v3::meta" because another
target with the same name already exists.
Call Stack (most recent call first):
CMakeLists.txt:9 (find_package)
CMake Error at /usr/lib/cmake/range-v3/range-v3-config.cmake:3 (add_library):
add_library cannot create imported target "range-v3::concepts" because
another target with the same name already exists.
Call Stack (most recent call first):
CMakeLists.txt:9 (find_package)
CMake Error at /usr/lib/cmake/range-v3/range-v3-config.cmake:4 (add_library):
add_library cannot create imported target "range-v3::range-v3" because
another target with the same name already exists.
Call Stack (most recent call first):
CMakeLists.txt:9 (find_package)
---
Failed <<< core [1.93s, exited with code 1]
The error seems to be caused by range-v3 itself so I think it might be good to temporarily disable exporting the range-v3 dependency until the issue is resolved upstream
Right now, the range-v3 dependency causes errors when a project depends on fp and range-v3 like this:
The error seems to be caused by range-v3 itself so I think it might be good to temporarily disable exporting the range-v3 dependency until the issue is resolved upstream