wheels: fix handling of cuda-tile dependency

[ChuckHastings]

(heavily edited by @jameslamb on Sep 8, 2026)

Contributes to rapidsai/build-planning#324

Wheel builds have been failing like this:

  -- Found Python: /pyenv/versions/3.14.7/bin/python (found version "3.14.7") found components: Interpreter
  CMake Error at build/py3-none-linux_x86_64/_deps/cuvs-src/cpp/cmake/modules/generate_cutile_kernels.cmake:61 (message):
    cuda.tile (cuTile Python) is required to build cuTile embedded kernels.
    Install cutile-python and cuda-tileiras (conda), or cuda-tile[tileiras]
    (pip).

    Interpreter: /pyenv/versions/3.14.7/bin/python

    Import error: Traceback (most recent call last):

      File "<string>", line 1, in <module>
        import cuda.tile

    ModuleNotFoundError: No module named 'cuda'
  Call Stack (most recent call first):
    build/py3-none-linux_x86_64/_deps/cuvs-src/cpp/cmake/modules/generate_cutile_kernels.cmake:229 (_cutile_kernels_setup)
    build/py3-none-linux_x86_64/_deps/cuvs-src/cpp/CMakeLists.txt:1161 (generate_cutile_kernels)


  -- Configuring incomplete, errors occurred!

(build link

Because:

1. cuVS now needs cuda-tile (Python library) at build time, since Generate cubins from cutile at build time and embed them in C++ DSO NVIDIA/cuvs#2548
2. libcugraph wheels build cuVS from source

This PR fixes that by adding a build-time dependency on cuda-tile for libcugraph.

Notes for Reviewers

Why no conda changes?

libcugraph conda builds do not compile cuVS from source, they link against pre-built packages.

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[jameslamb]

Started a thread with my comments from our offline conversation, so it's here in the GitHub history.

[jameslamb]

corrects the broken nightly builds.

I went to the build history to figure out what that means specifically. It looks like the failure in CI is CUDA 13 libcugraph wheel builds

  -- Found Python: /pyenv/versions/3.14.7/bin/python (found version "3.14.7") found components: Interpreter
  CMake Error at build/py3-none-linux_x86_64/_deps/cuvs-src/cpp/cmake/modules/generate_cutile_kernels.cmake:61 (message):
    cuda.tile (cuTile Python) is required to build cuTile embedded kernels.
    Install cutile-python and cuda-tileiras (conda), or cuda-tile[tileiras]
    (pip).

    Interpreter: /pyenv/versions/3.14.7/bin/python

    Import error: Traceback (most recent call last):

      File "<string>", line 1, in <module>
        import cuda.tile

    ModuleNotFoundError: No module named 'cuda'
  Call Stack (most recent call first):
    build/py3-none-linux_x86_64/_deps/cuvs-src/cpp/cmake/modules/generate_cutile_kernels.cmake:229 (_cutile_kernels_setup)
    build/py3-none-linux_x86_64/_deps/cuvs-src/cpp/CMakeLists.txt:1161 (generate_cutile_kernels)


  -- Configuring incomplete, errors occurred!

(build link

Changing just the all: group in dependencies.yaml wouldn't fix that, as those wheel builds are built without isolation using the dependencies defined in the py_build_libcugraph and py_rapids_build_libcugraph groups:

cugraph/ci/build_wheel_libcugraph.sh

Lines 15 to 26 in cb14128

	rapids-dependency-file-generator \
	--output requirements \
	--file-key "py_build_${package_name}" \
	--file-key "py_rapids_build_${package_name}" \
	--matrix "${matrix_selectors}" \
	| tee /tmp/requirements-build.txt
	rapids-logger "Installing build requirements"
	rapids-pip-retry install \
	-v \
	--prefer-binary \
	-r /tmp/requirements-build.txt

Short-term, if these wheels are needed at build time they need to be in the wheel-building dependency set.

Longer-term, it'd be great to switch libcugraph to building against libcuvs wheels to not need to keep making changes like this just for cuVS.

[jameslamb]

I will push a fix here.

[msarahan]

This is currently a blocker on the 26.10 release cycle. Please prioritize getting this merged @ChuckHastings. Thanks for your work on this, @jameslamb

[ChuckHastings]

This is currently a blocker on the 26.10 release cycle. Please prioritize getting this merged @ChuckHastings. Thanks for your work on this, @jameslamb

I think this is being superseded by #5654. But in either case, it is blocking all PRs planned for 26.10, so it's our highest priority to get this problem resolved.

[jameslamb]

This is superseded by #5654 and #5656