Build order for CUDA SDK

[adibbley]

Build order for CUDA SDK (issue reorder)

This is the build order for the full list of CUDA components. We are starting this process with cuda-nvcc, I will keep this up to date as we submit the remaining PRs.

I've separated this into 6 sections, each has some dependency on the previous. Hopefully this gives some clarity to how we've broken things down.

Also these will be added in a few passes:

• Compiler and associated packages.
• CUDA libraries
• Developer tools (debuggers, profilers, etc.)

---

Compiler

Build Order 1

• cuda-version ( Add cuda-version recipe #22053 )
• cuda-cudart ( Adding cuda-cudart #21723 )
• cuda-nvcc ( Adding cuda-nvcc recipe #21350 )
• cuda-nvrtc ( Adding cuda-nvrtc recipe #21951 )
• cuda-compat ( Adding cuda-compat recipe #21952 )
• cuda-cccl ( Adding cuda-cccl recipe #21953 )
• cuda-cuobjdump ( Adding cuda-cuobjdump, cuda-cuxxfilt, and cuda-nvprune recipes #21878 )
• cuda-cuxxfilt ( Adding cuda-cuobjdump, cuda-cuxxfilt, and cuda-nvprune recipes #21878 )
• cuda-nvprune ( Adding cuda-cuobjdump, cuda-cuxxfilt, and cuda-nvprune recipes #21878 )

Build Order 2

• cuda-compiler ( Add cuda-compiler recipe #23003 )
• cuda-nvcc_{{ target_platform }} ( Add cuda-nvcc_{{ target_platform }} cuda-nvcc-feedstock#1 )

---

Libraries

Build Order 1

• libcublas ( Add libcublas recipe #21901 )
• libcufft ( Add libcufft recipe #21902 )
• libcufile ( Add libcufile recipe #21908 )
• libcurand ( Add libcurand recipe #21916 )
• libcusolver ( Add libcusolver, libcusparse, and libnvjitlink recipes #21924 )
• libnvjitlink ( Add libcusolver, libcusparse, and libnvjitlink recipes #21924 )
• libcusparse ( Add libcusolver, libcusparse, and libnvjitlink recipes #21924 )
• cuda-nvml-dev ( Add cuda-nvml-dev recipe #22127 )
• cuda-nvtx ( Adding cuda-nvtx recipe #22052 )
• libnvjpeg ( Add libnvjpeg recipe #22128 )
• libnpp ( Add libnpp recipe #22832 )
• cuda-opencl ( Add cuda-opencl recipe #23002 )

Build Order 2

• cuda-libraries ( A cuda-libraries metapackages #23073 )
• cuda-libraries-dev ( A cuda-libraries metapackages #23073 )
• cuda-libraries-static (A cuda-libraries metapackages #23073 )

---

Devtools

Build Order 1

• cuda-profiler-api ( Adding cuda-profiler-api recipes #22125 )
• cuda-cupti ( Add cuda-cupti recipe #22355 )
• cuda-gdb ( Adding cuda-gdb recipe #22780 )
• cuda-nsight ( Add cuda-nsight recipe #22781 )
• cuda-nvdisasm ( Add cuda-nvdisasm, cuda-nvprof, cuda-nvvp recipes #22820 )
• cuda-nvprof ( Add cuda-nvdisasm, cuda-nvprof, cuda-nvvp recipes #22820 )
• cuda-nvvp ( Add cuda-nvdisasm, cuda-nvprof, cuda-nvvp recipes #22820 )
• cuda-sanitizer-api ( Adding cuda-sanitizer-api recipe #23000 )
• nsight-compute ( Add nsight-compute recipe #23001 )

Build Order 2

• cuda-command-line-tools ( Add cuda metapackage recipes #23178 )

Build Order 3

• cuda-minimal-build ( A cuda-libraries metapackages #23073 )
• cuda-runtime ( A cuda-libraries metapackages #23073 )
• cuda-visual-tools ( Add cuda metapackage recipes #23178 )

Build Order 4

• cuda-tools ( Add cuda metapackage recipes #23178 )

Build Order 5

• cuda-toolkit ( Add cuda metapackage recipes #23178 )
• nvidia-gds ( A cuda-libraries metapackages #23073 )

Build Order 6

• cuda ( Add cuda metapackage recipes #23178 )

---

Additional products to add after CUDA:

Ready to package:

• cuDNN
• cuTENSOR
• nvCOMP ( Create nvcomp recipe. #23034 )

Can be packaged (missing source redist):

• TensorRT ( split out as issue: Package request: TensorRT #25661 )

Rebuild in feedstocks:

• CUTLASS ( Rebuild for CUDA 12 cutlass-feedstock#10 )
• NCCL ( Build with CUDA 12 nccl-feedstock#85 )

---

cc @jakirkham

[jakirkham]

cc @conda-forge/core

[kkraus14]

@adibbley @jakirkham would it be possible to add cuda-compat to this list? Allowing users to take advantage of the forward compatibility package from conda would be quite nice.

[adibbley]

The cuda-compat package contents come from the nvidia-driver build, which is why we don't currently have this for conda packaging. It looks like we should be able to create a cuda-compat component which points to a driver build (example) and only include the forward compatibility bits.

[jaimergp]

Awesome! So excited to see this!

With respect to the naming conventions, am I assuming correctly that underscore-separated names are "component packages" but dash-separated ones are more like "collections of components" packages? Is there an intention behind this or something that happened organically? It might be confusing to adopt two different naming conventions unless there's a good reason.

[adibbley]

Our package names shouldn't have underscores in them, I will update above.

[mikemhenry]

This is great! I am really interested in getting cuda 12 on conda-forge, is there anything I can do to help?

[jakirkham]

Thanks for the offer! Help reviewing PRs would be great.

Currently we have this one ( #21350 ). There will be more (as the list suggests) once we get that in.

[jakirkham]

Just a note, we've restructured the list above to clarify priority. Getting a working compiler (with needed dependencies) is the first step and then libraries. Other dev tools will come later on.

Also there are a couple packages not currently addressed that we will need to figure out somehow. They've been listed at the bottom.

[raimis]

@jakirkham thanks for the clarification. Do you have any idea when we can expect each phase to be completed?