| 3 May 2025 |
 Alyssa Ross | Assuming I'm correctly understanding what you mean by "target check"? | 17:10:12 |
 Randy Eckenrode | The one that spams lots of warnings when you clang-wrapper -target <some triple>, and the triple is different from what the wrapper was built for. | 17:11:16 |
| Alyssa Ross | Oh that sounds fine | 17:11:46 |
| Alyssa Ross | Assuming LLVM treats them the same | 17:12:00 |
| Randy Eckenrode | You can change the deployment target a bunch of different ways. The way Swift does it (and when invoking Clang) is via the triple. The wrapper tries to set the target via -mmacos-version-min=. I think there’s another way it can also fall back to do. | 17:12:03 |
| Randy Eckenrode | So maybe Darwin can settle on following Swift’s lead and consolidate all those. Probably a 25.11 thing. | 17:12:38 |
| Randy Eckenrode | It would also fix the following warnings when SwiftPM invokes Clang.
Warning: supplying the --target arm64-apple-macosx10.13 != arm64-apple-darwin argument to a nix-wrapped compiler may not work correctly - cc-wrapper is currently not designed with multi-target compilers in mind. You may want to use an un-wrapped compiler instead.
| 17:14:42 |
| Randy Eckenrode | * It would also fix the following warnings when SwiftPM invokes Clang.
clang: warning: overriding '-mmacos-version-min=11.3' option with '-target arm64-apple-macosx10.13'
| 17:15:07 |
