| 28 Jun 2025 |
 emily | it reads from the non mangled var like everything else | 12:51:47 |
 Randy Eckenrode | CMake? Are you sure? I’m pretty sure I’ve gotten deployment target mismatch warnings until I set it explicitly to match what I want it to be. | 12:54:50 |
| Randy Eckenrode | My preference would be for sysroots with text-based stubs generated on platforms that support them. AFAIK stubs are faster to link than binaries, and it would ensure the install names are correct. Having everything together in a sysroot also works better with Clang modules. | 12:57:33 |
| Randy Eckenrode | (Which Swift leverages heavily.) | 12:57:41 |
| emily | In reply to @reckenrode:matrix.org
CMake? Are you sure? I’m pretty sure I’ve gotten deployment target mismatch warnings until I set it explicitly to match what I want it to be. "If not set explicitly the value is initialized by the MACOSX_DEPLOYMENT_TARGET environment variable, if set, and otherwise computed based on the host platform." | 12:59:42 |
| emily | the issue is that a lot of builds set it manually | 12:59:49 |
| Randy Eckenrode | So if we specify it, it overrides theirs? | 13:00:21 |
| emily | yes | 13:00:32 |
| emily | In reply to @reckenrode:matrix.org
My preference would be for sysroots with text-based stubs generated on platforms that support them. AFAIK stubs are faster to link than binaries, and it would ensure the install names are correct. Having everything together in a sysroot also works better with Clang modules. I think many things hardcode .dylib and .so unfortunately | 13:00:58 |
