| 6 Jan 2025 |
 emily | I guess the per-platform bootstrap stages don't necessarily know whether cc is going to be set in the stdenv? 🤔 | 19:48:16 |
| emily | right now we do this kind of thing
thisStdenv = import ../generic {
name = "${name}-stdenv-darwin";
buildPlatform = localSystem;
hostPlatform = localSystem;
targetPlatform = localSystem;
inherit config;
extraBuildInputs = [ prevStage.apple-sdk ];
inherit extraNativeBuildInputs;
| 19:48:50 |
| emily | but including the SDK in stdenvNoCC pulls in a bunch of stuff | 19:49:02 |
 Randy Eckenrode | Did the old stdenvNoCC include CoreFoundation? | 19:53:05 |
| Randy Eckenrode | It’s picking up extraBuildPackages? | 19:53:28 |
| Randy Eckenrode | * It’s picking up extraBuildInputs? | 19:53:40 |
| emily | https://github.com/NixOS/nixpkgs/issues/371465 | 19:54:30 |
| Randy Eckenrode | I saw the issue. Was this not a problem no one noticed before because it was just the CoreFoundation headers and stubs? | 19:55:11 |
| Randy Eckenrode | * | 19:55:41 |
| Randy Eckenrode | The SDK pulls in a toolchain because it symlinks some stuff in $DEVELOPER_DIR/usr/bin because Chromium. | 19:57:06 |
| Randy Eckenrode | Isn’t the easy fix to drop extraBuildInputs on Darwin? | 19:57:40 |
| Randy Eckenrode | * Isn’t the easy fix to drop extraBuildInputs from stdenvNoCC on Darwin? | 19:57:56 |
| emily | yes | 19:58:31 |
| emily | I was trying to figure out how to do this | 19:58:34 |
