Rebuild for qt515

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update qt515.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/3754238446, please use this URL for debugging.}

[conda-forge-linter]

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.

[h-vetinari]

So this only fails with win+CUDA it seems:

D:\bld\prismatic_split_1671679927246\_h_env\Library\include\qt\QtCore\qmutex.h(133): error: defaulted default constructor cannot be constexpr because the corresponding implicitly declared default constructor would not be constexpr

There's also

nvcc warning : The -std=c++11 flag is not supported with the configured host compiler. Flag will be ignored.

so perhaps this has to be adapted to /std:c++11 (or some other C++ standard)

[ericpre]

So this only fails with win+CUDA it seems:

D:\bld\prismatic_split_1671679927246\_h_env\Library\include\qt\QtCore\qmutex.h(133): error: defaulted default constructor cannot be constexpr because the corresponding implicitly declared default constructor would not be constexpr

This seems to be related to a MSVS bug, possibly fixed in VS2022: https://forum.qt.io/topic/111793/how-to-resolve-error-of-qmutex-h/17

What can be done?

[h-vetinari]

What can be done?

If indeed that bug is solved by vs2022, you can try to add:

c_compiler:                    # [win]
- vs2022                       # [win]
cxx_compiler:                  # [win]
- vs2022                       # [win]

to recipe/conda_build_config.yaml and rerender.

[ericpre]

@h-vetinari, I gave a go at using VS2022 in https://github.com/conda-forge/prismatic_split-feedstock/pull/34 and there is an error with finding cl.exe , do you know if there any example of recipe using vs2022?

[h-vetinari]

@h-vetinari, I gave a go at using VS2022 in #34 and there is an error with finding cl.exe , do you know if there any example of recipe using vs2022?

It's very possible that there are still some rough edges around VS2022 support in conda-forge. I don't think there's any feedstock using it yet.

[conda-forge-webservices[bot]]

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.

[ericpre]

@conda-forge-admin, please rerun bot

[regro-cf-autotick-bot]

Due to the bot-rerun label I'm closing this PR. I will make another one as appropriate. This was generated by https://github.com/regro/cf-scripts/actions/runs/5058190660