Configuring CMake fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cmake, cpp
- Domain
- build-system, testing
Research direction
Reproduce the first and subsequent CMake configurations with STD_BUILD_TESTS disabled, including the Linux case. Inspect build/_deps/stdexec-src/test/CMakeLists.txt around lines 140-142 and determine why the later configure cannot find /contrib/Catch.cmake or catch_discover_tests; done means repeated configuration succeeds without these errors.
Written by the indexing model from the issue text.
Description
Configuring CMake with stdexec as a dependency works the first time entirely from scratch (on Mac/Windows). However, subsequent calls to CMake will produce the following error:
CMake Error at build/_deps/stdexec-src/test/CMakeLists.txt:140 (include):
include could not find requested file:
/contrib/Catch.cmake
CMake Error at build/_deps/stdexec-src/test/CMakeLists.txt:142 (catch_discover_tests):
Unknown CMake command "catch_discover_tests".
Deleting the cache seems to work, except on Linux which seems to have this problem more persistently.
We're configuring with STD_BUILD_TESTS turned off.
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 43
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/stdexec
-
inline_scheduler's namespace-scope static_assert fails under nvcc (private nested __sender access) Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Opencoarray
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·