You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched open requests and couldn't find a duplicate
What is the idea?
The cran skeleton currently says:
{{% set posix = 'm2-' if win else '' %}}
{{% set native = 'm2w64-' if win else '' %}}
and also uses the m2w64 prefix elsewhere for setting the compilers.
The should be parameterized.
Of course, the default action should be to create a functionally identical recipe. Only if you define the parameters should the strings change.
Why is this needed?
If conda PR conda/conda#13649 is merged then the Anaconda package prefixes will likely change to msys2- and one or more of ucrt64-, clang64-, mingw64- etc. matching the upstream MSYS2 environment names.
What should happen?
Further to simple parameterization, it would be beneficial if we could distinguish between MSYS2 build and MSYS2 host resources, so something like:
{{% set posix = '{msys2_msys_pkg_prefix}' if win else '' %}}
{{% set native_build = '{msys2_mingw_w64_build_pkg_prefix}' if win else '' %}}
{{% set native_host = '{msys2_mingw_w64_host_pkg_prefix}' if win else '' %}}
Checklist
What is the idea?
The
cran
skeleton currently says:and also uses the
m2w64
prefix elsewhere for setting the compilers.The should be parameterized.
Of course, the default action should be to create a functionally identical recipe. Only if you define the parameters should the strings change.
Why is this needed?
If conda PR conda/conda#13649 is merged then the Anaconda package prefixes will likely change to
msys2-
and one or more ofucrt64-
,clang64-
,mingw64-
etc. matching the upstream MSYS2 environment names.What should happen?
Further to simple parameterization, it would be beneficial if we could distinguish between MSYS2 build and MSYS2 host resources, so something like:
and for the compilers, the likes of:
together with a change to what
gcc-libs
refers to in the recipe:Additional Context
I've started a PR!
The text was updated successfully, but these errors were encountered: