Add a news entry for macOS SDK directory change #2684
Conversation
See conda-forge/conda-smithy#2430. Signed-off-by: Michał Górny <[email protected]>
✅ Deploy Preview for conda-forge-previews ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
news/2025-12-04-osx-sdk-dir.md
Outdated
|
|
||
| Starting with conda-smithy 3.53.4, the build scripts will no longer use the system macOS SDK directory by default. The CI systems will use a dedicated `/opt/conda-sdks` directory, while users performing local builds will need to choose a writable directory, and provide the path to it via `OSX_SDK_DIR` environment variable. | ||
|
|
||
| This change may result in some build systems, particularly CMake, storing paths to this temporary build directory in installed metadata. Feedstocks will need to substitute the stored paths with path-agnostic solutions (for example, see [substitutions in openpmd-api-feedstock](https://github.com/conda-forge/openpmd-api-feedstock/blob/15f9b3648f087d3e06331d6ec9ddff0710300593/recipe/build.sh#L100-L107)) or the correct sysroot paths (for example, see [substitutions in cartographer-feedstock](https://github.com/conda-forge/cartographer-feedstock/blame/1812f8c13bccbad20daf6ba079f7722cace93a15/recipe/conda_build_config.yaml#L19-L23). |
There was a problem hiding this comment.
Based on the discussion in conda-forge/conda-smithy#2430, this should only be necessary for people compiling against our artefacts outside conda-forge, not in our CI. I'd like to reflect that here, otherwise it sounds like a massive deterioration of the feedstock maintenance situation (which is why I had written this).
Also, please wrap your lines at some finite length (something <130 characters due to the way GH's interface works)
There was a problem hiding this comment.
My understanding is that it would also affect a transition period when some feedstocks are rendered with this change, and others still haven't been and therefore may embed wrong paths. And either way, I think fixing paths is the technically correct thing to do, even if it wasn't strictly necessary when the OSX SDK directory paths happened to match.
There was a problem hiding this comment.
As for wrapping, I've followed 2025-10-15-conda-forge-discourse-read-only.md but perhaps that just happened to have the wrapping length beyond the paragraph length :-). I'll reflow.
Signed-off-by: Michał Górny <[email protected]>
2 participants
PR Checklist:
docs/orcommunity/, you have added it to the sidebar in the corresponding_sidebar.jsonfileSee conda-forge/conda-smithy#2430.