Add native win-arm64 support - #93
Conversation
|
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 ( |
|
won't this have the same issues as conda-forge/rattler-build-feedstock#158 ? |
|
We are now using reqwest 0.13 so I hope that will solve the issue |
|
Blocked on conda-forge/cross-python-feedstock#95 |
…a-forge-pinning 2026.07.15.16.57.46 Other tools: - conda-build 26.5.0 - rattler-build 0.65.1 - rattler-build-conda-compat 1.4.14
2afeaba to
eb16872
Compare
…to claude/add-win-arm64-support-kyUqx
|
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 ( I do have some suggestions for making it better though... For recipe/recipe.yaml:
tests:
- requirements:
run:
- abi3audit
script:
- if: unix
then: abi3audit $SP_DIR/mypackage.abi3.so -s -v --assume-minimum-abi3 ${{ python_min }}
else: abi3audit %SP_DIR%/mypackage.pyd -s -v --assume-minimum-abi3 ${{ python_min }}
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/31332937382. Examine the logs at this URL for more detail. |
|
|
|
depends on conda-forge/cmake-feedstock#267 |
|
╰─▶ Cannot solve the request because of: No candidates were found for make |
Builds
py-rattlernatively on GitHub'swindows-11-armrunners. The only recipe change beyond the CI setup is one environment variable thataws-lc-sysneeds on that platform.aws-lc-sys
aws-lc-sysdoes not build on win-arm64.cl.execannot assemble the generatedwin-aarch64perlasm, so it skips the files and the link then fails on objects that were never produced:aws-lc-sysknows about this and since 0.40.0 (aws/aws-lc-rs#1060) locatesclang-clin the Visual Studio installation by itself. That only happens whenCCis unset:The conda-forge activation sets
CC=cl.exe, so the discovery is skipped and we land back on the one compiler that cannot build this target. SettingAWS_LC_SYS_CC_aarch64_pc_windows_msvc=clang-cl.exetakes priority overCCand gets us to the same compiler upstream would have picked. The variable is target-scoped, so it is inert everywhere else. The guard is unchanged in 0.44.0, so bumping the crate does not help.conda-forge/uv-feedstock#369 and conda-forge/pixi-build-python-feedstock#27 hit the same problem and route around it with
AWS_LC_SYS_CMAKE_BUILDER=1, whose cmake builder picks theClangCLtoolset. That works too, but needs acmakefor win-arm64 (conda-forge/cmake-feedstock#267) and there is nothing else in this recipe that wants cmake.Blocked on
abi3audittest needs native builds of transitive dependencies such asujsonand Brotli.Merged and no longer blocking: conda-forge/conda-smithy#2622, conda-forge/cargo-bundle-licenses-feedstock#29, conda-forge/cargo-auditable-feedstock#11, conda-forge/maturin-feedstock#180, conda-forge/python-abi3-feedstock#11.
Validation
conda-smithy lint --conda-forge ., and a second rerender produces no changes.clang-cloverride, after temporarily provisioning the unavailable tooling from win-64 under emulation. It confirmed thatpy-rattlercompiles, packages, imports and passes its ABI audit natively on win-arm64. Those bootstrap workarounds are intentionally not part of this PR.