Skip to content

Align conda-recipe-cf with the conda-forge feedstock - #253

Open
antonwolfy wants to merge 2 commits into
masterfrom
align-cf-recipe-stdlib
Open

antonwolfy wants to merge 2 commits into
masterfrom
align-cf-recipe-stdlib

Conversation

@antonwolfy

Copy link
Copy Markdown
Collaborator

Aligns conda-recipe-cf with mkl-service-feedstock, so the conda-forge CI job tests the package against the same baseline conda-forge ships.

Stdlib baseline (conda_build_config.yaml):

  • Linux: sysroot 2.28 → 2.17, the conda-forge default (conda-forge mkl itself only requires __glibc >=2.17)
  • macOS: set c_stdlib_version and MACOSX_DEPLOYMENT_TARGET to 11.0. Neither was set, so the compiler targeted 10.9 while the newest macosx_deployment_target (26.0) stamped the package with __osx >=26.0

Tidy-ups (meta.yaml, bld.bat):

  • Drop the unused wheel host dependency (the build scripts only run pip install, and meson-python builds the wheel itself) and the pip >=25.0 floor
  • Add license_family: BSD, as in the feedstock
  • Remove a stale comment from bld.bat

Build against glibc 2.17 on Linux and a macOS 11.0 deployment target,
matching conda-forge's global pinning used by mkl-service-feedstock.

Previously Linux used sysroot 2.28, and on macOS neither
c_stdlib_version nor MACOSX_DEPLOYMENT_TARGET was set: the compiler
targeted 10.9 while the newest macosx_deployment_target (26.0) stamped
the package with __osx >=26.0. CI therefore could not catch regressions
at the baseline conda-forge actually ships.
- Drop the unused `wheel` host dependency: the build scripts only run
  `pip install`, and meson-python builds the wheel itself
- Drop the `pip >=25.0` floor, which is not an upstream requirement
- Add `license_family: BSD`, as in mkl-service-feedstock
- Remove a stale comment from bld.bat
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant