Skip to content

docs: full CUDA toolkit (NVRTC dev libs) required to build the extension#208

Open
JinukMoon wants to merge 1 commit into
PASSIONLab:mainfrom
JinukMoon:docs-nvrtc-toolkit-requirement
Open

docs: full CUDA toolkit (NVRTC dev libs) required to build the extension#208
JinukMoon wants to merge 1 commit into
PASSIONLab:mainfrom
JinukMoon:docs-nvrtc-toolkit-requirement

Conversation

@JinukMoon

Copy link
Copy Markdown

What

Adds an installation-docs note that building the C++ extension requires a full CUDA toolkit including the NVRTC development libraries, with the exact failure signature and the CUDAToolkit_ROOT workaround.

Why

Follow-up to #207 (item 2 of my 0.6.8 test report there): on a toolchain that provides only the compiler — e.g. conda's cuda-nvcc package alone — the CMake build fails with

target_link_libraries ... CUDA::nvrtc but the target was not found

because openequivariance/CMakeLists.txt links CUDA::nvrtc. The failure is easy to hit in conda-managed environments (where cuda-nvcc is the idiomatic way to get nvcc) and the error message doesn't hint at the fix. Verified on torch 2.8.0+cu128 / cp311 / RTX 4060 Ti: setting CUDAToolkit_ROOT to a full toolkit (/usr/local/cuda-12.8) resolves it.

As suggested by @asglover in #207 — happy to adjust wording or placement.

🤖 Generated with Claude Code

A compiler-only toolchain (e.g. conda's cuda-nvcc alone) fails the CMake
build with 'CUDA::nvrtc but the target was not found' (CMakeLists.txt links
CUDA::nvrtc). Document the requirement and the CUDAToolkit_ROOT workaround,
as suggested in PASSIONLab#207.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant