Rebuild cuda-bindings with and without cuda-nvvm#130
Rebuild cuda-bindings with and without cuda-nvvm#130bdice wants to merge 8 commits intoconda-forge:mainfrom
Conversation
…3.0 using cuda-nvvm.
…nda-forge-pinning 2025.07.10.09.01.51
…nda-forge-pinning 2025.07.10.09.01.51
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16227380041. Examine the logs at this URL for more detail. |
|
@conda-forge-admin, please rerender |
|
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16218898807. Examine the logs at this URL for more detail. |
|
Closing in favor of #131. |
Checklist
0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)I discussed #129 with @kkraus14 and we decided to try splitting the build of
cuda-bindings.This PR splits the build of
cuda-bindingsinto CUDA >=12.0,<12.2 usingcuda-nvcc-impland >=12.2,<13.0 usingcuda-nvvm.This is needed because the
cuda-nvvmpackage does not exist for CUDA >=12.0,<12.2, and we must usecuda-nvcc-implto get the same components.This is my first time doing significant changes to this feedstock, so I'd like a careful review of how I'm using
conda_build_config.yaml. There are some portions of this feedstock that are used to control the build ofcuda-bindingsvs.cuda-core.