don't unset some VS-related variables after activation#95
Conversation
|
@isuruf, if you are online, PTAL. |
|
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/16362318596. Examine the logs at this URL for more detail. |
|
Let's revert the whole PR and get back to this after all the anaconda.org issues and cmake 4 issues die down |
Felt like reinstating VSINSTALLDIR would have been worth a shot, but here you go: #96 |
That should be the case now. |
|
Ping @isuruf |
|
This runs into too-long filenames I'm reviving an old smithy PR that fixes this (conda-forge/conda-smithy#2233). |
|
Ping @isuruf |
|
Ping @isuruf |
| popd | ||
|
|
||
| :: unset auxiliary variables | ||
| set "CMAKE_GEN=" |
There was a problem hiding this comment.
It looks like CMAKE_GEN is being by used conda-forge recipes even though it's not supposed to be.
There was a problem hiding this comment.
It looks like that's limited to 3 feedstocks. Sounds like we could just fix those?
There was a problem hiding this comment.
Yeah, let's fix those first. I'd hate to break scikit-build-core package.since it's used in an activate script.
|
@isuruf, now that conda-forge/scikit-build-core-feedstock#67 is merged, this should be good to go? |
|
Ping @isuruf |
…nda-forge-pinning 2025.07.17.18.51.38
|
@conda-forge/core I'm not able to get a response here, and willing to join as maintainer - could someone please merge? I have the second-most commits on this feedstock, so arguably already de facto a maintainer anyway. :) |
|
Sigh, this still leads to breakage it seems (at least it looks very similar to #94), e.g. in conda-forge/mimalloc-feedstock#39. I'll revert this yet again in #99 |
This reverts commit 4f9e21e.
This reverts commit 4f9e21e.
In the context of #94, we need to publish new builds, because conda-forge/admin-requests#1460 isn't taking effect due to conda-forge/conda-forge-repodata-patches-feedstock#986.
I started out with wanting to revert #93, but then noticed that one of the changes of that PR was that we're unsetting
VSINSTALLDIR, which looks like it would exactly explain the sort of "forgot the path to MVSC toolchain" issues we're seeing in #94.So reinstate variables that are very likely related to the issues there. If that still doesn't work out, we can revert #93
Fixes #94
Fixes #91