-
-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Unable to use MinGW instead of MSVC for building packages on Windows #2337
Comments
Do you have a PR on All R packages build through MinGW, so maybe have a look at their recipes. Recently we've been transitioning to UCRT, so some of the recipes might be in flux. For example, here's a recent submission without UCRT. I believe it's mostly a matter of using |
Hello! Thank you for the reply!
I have just made one: conda-forge/staged-recipes#27974
I tried many things from that repository, but they didn't help. I also noticed that there is a problem with the CI build of that PR on Windows. However, I am not sure if it’s caused by MinGW problems.
When I try something like I tried to build conda packages locally on my Windows machine by running the command (according to the documentation):
I also tried running just
But there was no difference. Build machine info:
Conda build environment info:
Conda environment packages:
|
As I expected, the CI build on the Windows server crashed at the extension compilation step because MSVC was called instead of the MinGW compiler:
The compiler('m2w64_cxx') setting was used in the recipe, but it was ignored by conda. What steps should I try next to fix the Windows build? |
I believe the issue is that those definitions are derived from conda_build_config.yamlin the conda-forge-pinning-feedstock repo. Those still use the old definitions because this migration https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/main/recipe/migrations/r-base44_and_m2w64-ucrt.yaml is still not completed. If I understand correctly, you need to manually enter the new definitions from that migration in your project's conda_build_config.yaml. |
Thank you for the answer! Unfortunately, it didn’t work. It seems that we need to wait for official MinGW support from the conda-forge team. |
Your question:
Hello!
I am trying to contribute the Lets-Plot package to conda-forge.
That project is based on Kotlin Native with Python API.
The issue I am facing is that
conda-build
defaults to using MSVC on Windows, but the library needs to be built with MinGW, because Kotlin Native supports only MinGW as a build target for the Windows platform.Even after configuring
meta.yaml
,bld.bat
, andsetup.py
to explicitly call MinGW,conda-build
continues to invoke MSVC.Steps taken:
bld.bat
to configure MinGW.setup.py
to link to MinGW binaries.conda-build
continues to use MSVC.Is there an official way to force
conda-build
to use MinGW for Windows builds? Or are there any known workarounds or future plans to support this?The text was updated successfully, but these errors were encountered: