Allow compiling with vs2022 by xhochy · Pull Request #50 · conda-forge/rust-activation-feedstock (original) (raw)

The background is the solving failure I see in conda-forge/librsvg-feedstock#110 where vs2022 is requested as a compiler. This would make the activation package more "open" but also would pull in vs2022 probably as default?

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.

Choose a reason for hiding this comment

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

LGTM

This would make the activation package more "open" but also would pull in vs2022 probably as default?

AFAIU it'll pull in vs2022 if there's only {{ compiler("rust") }}; as soon as there's {{ compiler("c|cxx") }} in the build env that resolves to vs2019, it would resolve to that instead.

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})