Add recipe/conda_build_config.yaml to use vs2017

conda-forge / graphblas-feedstock

A conda-smithy repository for graphblas.

BSD 3-Clause "New" or "Revised" License

2 stars 6 forks source link

Closed eriknw closed 1 year ago

eriknw commented 1 year ago

Checklist

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

I think recipe/conda_build_config.yaml is the correct way to specify which compiler to use: https://conda-forge.org/docs/maintainer/knowledge_base.html#using-vs2019

conda-forge-linter commented 1 year ago

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.

eriknw commented 1 year ago

@conda-forge-admin, please rerender

github-actions[bot] commented 1 year ago

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

eriknw commented 1 year ago

This is a followup to https://github.com/conda-forge/graphblas-feedstock/pull/45, where I manually forced vs2017. This PR adds a config file so rerender should be correct and use vs2017 instead of updating to vs2019.