| 13 Jan 2026 |
 emily | there's even header files in there | 01:28:13 |
| emily | but ofc if you made the output less dumb in the rework that's another matter :) | 01:28:23 |
 Randy Eckenrode | The reason why LLD currently “works” is it relies on Clang to pass the correct flags. It’s not even wrapped. | 01:28:29 |
| Randy Eckenrode | $ nix build -f . swiftPackages.stdlib^\*
$ ls result/**
result/lib/lib_InternalSwiftStaticMirror.dylib*
result/lib/libswift_Builtin_float.dylib*
result/lib/libswift_Concurrency.dylib*
result/lib/libswift_Differentiation.dylib*
result/lib/libswift_RegexParser.dylib*
result/lib/libswift_StringProcessing.dylib*
result/lib/libswift_Volatile.dylib*
result/lib/libswiftCompatibilitySpan.dylib@
result/lib/libswiftCore.dylib*
result/lib/libswiftDistributed.dylib*
result/lib/libswiftObservation.dylib*
result/lib/libswiftRegexBuilder.dylib*
result/lib/libswiftRemoteMirror.dylib*
result/lib/libswiftRuntime.dylib*
result/lib/libswiftSwiftOnoneSupport.dylib*
result/lib/libswiftSynchronization.dylib*
result/lib/swift-6.2/macosx/libswiftCompatibilitySpan.dylib*
result/lib:
lib_InternalSwiftStaticMirror.dylib* libswiftDistributed.dylib*
libswift_Builtin_float.dylib* libswiftObservation.dylib*
libswift_Concurrency.dylib* libswiftRegexBuilder.dylib*
libswift_Differentiation.dylib* libswiftRemoteMirror.dylib*
libswift_RegexParser.dylib* libswiftRuntime.dylib*
libswift_StringProcessing.dylib* libswiftSwiftOnoneSupport.dylib*
libswift_Volatile.dylib* libswiftSynchronization.dylib*
libswiftCompatibilitySpan.dylib@ swift-6.2/
libswiftCore.dylib*
result/lib/swift-6.2:
macosx/
result/lib/swift-6.2/macosx:
libswiftCompatibilitySpan.dylib*
| 01:29:17 |
| emily | an output with the runtime libraries required for Swift binaries (on Linux only, I guess?) would make sense, but the current lib ain't it | 01:29:20 |
| emily | do those .dylibs even get used on macOS, where the Swift runtime is part of the OS dyld cache? | 01:29:44 |
| Randy Eckenrode | All the Swift modules, embedded stuff, headers, and shims are in the dev output. | 01:29:57 |
| emily | shouldn't it be the out output, as it's consumed by the compiler rather than things taking the compiler as a build input 🤔 | 01:30:26 |
| Randy Eckenrode | They do some funky stuff to forward to the system. I don’t think we can avoid having them. We need the Span compatibility dylib for back deployment to 14.x and 15.x. | 01:30:33 |
| Randy Eckenrode | The stdlib is a separate derivation. It has out and dev outputs. | 01:31:03 |
| emily | ah | 01:31:11 |
| Randy Eckenrode | The embedded stuff is kind of weird. It lets you build “bare metal” Darwin applications. | 01:31:58 |
| Randy Eckenrode | Whatever the hell that means. | 01:32:03 |
