Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build order for CUDA SDK #21382

Closed
48 of 49 tasks
adibbley opened this issue Nov 30, 2022 · 30 comments
Closed
48 of 49 tasks

Build order for CUDA SDK #21382

adibbley opened this issue Nov 30, 2022 · 30 comments

Comments

@adibbley
Copy link
Contributor

adibbley commented Nov 30, 2022

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

Build Order 2


Libraries

Build Order 1

Build Order 2


Devtools

Build Order 1

Build Order 2

Build Order 3

Build Order 4

Build Order 5

Build Order 6


Additional products to add after CUDA:

Ready to package:

Can be packaged (missing source redist):

Rebuild in feedstocks:


cc @jakirkham

@mariusvniekerk mariusvniekerk pinned this issue Nov 30, 2022
@jakirkham
Copy link
Member

cc @conda-forge/core

@kkraus14
Copy link
Contributor

@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
Copy link
Contributor Author

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
Copy link
Member

jaimergp commented Dec 5, 2022

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
Copy link
Contributor Author

adibbley commented Dec 5, 2022

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

@mikemhenry
Copy link
Contributor

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

@jakirkham
Copy link
Member

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
Copy link
Member

jakirkham commented Jan 25, 2023

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
Copy link

raimis commented Jan 26, 2023

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

This was referenced May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests