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

Add migrator for CUDA on Windows #914

Merged
merged 2 commits into from
Nov 16, 2020

Conversation

jaimergp
Copy link
Member

@jaimergp jaimergp commented Nov 1, 2020

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

PR created in the context of bringing nvcc on Windows. Related PRs:

@jaimergp jaimergp requested a review from a team as a code owner November 1, 2020 18:31
@conda-forge-linter
Copy link

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 (recipe) and found it was in an excellent condition.

- gcc # [linux]
- clang # [osx]
# part of a zip_keys: c_compiler, cxx_compiler, cuda_compiler_version
- vs2015 # [win]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't support vs2015 anymore

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That will simplify the migration, but unfortunately it'll mean that CUDA 9.2 won't get support on Windows :/

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, but @conda-forge/core made a decision to stop supporting it and going back is not possible without rebuilding all of the dependencies of a package needing CUDA 9.2.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CUDA 9.2 headers could be patched, but that doesn't look like a good idea.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically you can make it work by installing vc140 toolchain inside VS2017 and making sure vs2015_win-64 use the VS2017 installation of vc140.

@jaimergp jaimergp mentioned this pull request Nov 1, 2020
11 tasks
@jaimergp
Copy link
Member Author

Is there anything else to be added here?

@CJ-Wright
Copy link
Member

I think this looks ok, would you be able to baby sit things for a bit?

@jaimergp
Copy link
Member Author

Babysitting as in helping other repos set up their Windows integrations?

@CJ-Wright
Copy link
Member

More as in, watch the PRs the bot makes for this, if they seem incorrect (either in the build or the order) ping us and open a revert PR (or fix the migrator).

@jaimergp
Copy link
Member Author

Sure, that I can do!

@CJ-Wright
Copy link
Member

@isuruf is ok by you?

@CJ-Wright CJ-Wright merged commit 1a5ce55 into conda-forge:master Nov 16, 2020
@jakirkham
Copy link
Member

Thanks for working on this Jaime! 😄

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.

5 participants