Open spevans opened 4 years ago
@swift-ci create
Dropping in here to note that this bug makes it no longer possible to work with the overlay and the open-source implementation simultaneously since the adoption of @_spi(Foundation)
in the overlay, which deliberately requires the use of a snapshot toolchain to build. This is particularly unfortunate as (a) these two projects are part of the same repo yet ToT can't be built with a single toolchain; and (b) it's actively desirable to keep these two projects in sync but the use of @_spi
in conjunction with this bug throws up a barrier to that.
Using the default Xcode toolchains works without issue.
I am using Xcode 13.3.1 and encountering issues building the SwiftFoundation
target from corelibs foundation, following the Getting Started guide. They are quite confusing as some steps mention using the latest snapshot, but then there are notes stating to use the current Xcode version.
What's the current guidance?
Environment
macOS 10.15.3 Xcode 11.3.1, 11.4 (beta)Additional Detail from JIRA
| | | |------------------|-----------------| |Votes | 0 | |Component/s | Foundation | |Labels | Bug | |Assignee | None | |Priority | Medium | md5: ec29f3810e07302629468489d098f6beIssue Description:
Running
TestFoundation
in Xcode using a snapshot toolchain egswift-swift-DEVELOPMENT-SNAPSHOT-2020-02-08-a-osx
results in a runtime error although it compiles and builds successfully.I believe this ultimately due to the version check performed in
swift::_swift_stdlib_operatingSystemVersion
which ends up calling directly into CoreFoundation without__CFInitialize()
being called first. This is most likely due to how CoreFoundation is built as part of theswift-corelibs-foundation
such that its constructor doesnt call this function.Using the default Xcode toolchains works without issue.