You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of Xcode 10.2 beta 4, the swift_static directory inside Xcode has disappeared. When you attempt to use --static-swift-stdlib with Swift Package Manager this seems to be a very intentional change:
% swift build --static-swift-stdlib
warning: Swift compiler no longer supports statically linking the Swift libraries. They're included in the OS by default starting with macOS Mojave 10.14.4 beta 3. For macOS Mojave 10.14.3 and earlier, there's an optional Swift library package that can be downloaded from "More Downloads" for Apple Developers at https://developer.apple.com/download/more/
In order to continue supporting older OS versions with CLIs, we'll need to add the rpath to the Swift libraries inside Xcode (or the system location for 10.14.4 and up). This change will also affect rules_apple which uses the static functionality for macOS CLIs and dylibs.
The text was updated successfully, but these errors were encountered:
There's a tiny workaround in there for older OSes that points the rpath to the Swift library directory inside Xcode so that local builds (like host tools written in Swift) still run without needing the extra package from Apple installed, but I'll remove that eventually.
As of Xcode 10.2 beta 4, the
swift_static
directory inside Xcode has disappeared. When you attempt to use--static-swift-stdlib
with Swift Package Manager this seems to be a very intentional change:In order to continue supporting older OS versions with CLIs, we'll need to add the
rpath
to the Swift libraries inside Xcode (or the system location for 10.14.4 and up). This change will also affect rules_apple which uses the static functionality for macOS CLIs and dylibs.The text was updated successfully, but these errors were encountered: