What's the status on this? How is this task linked to moving swift-corelibs-foundation to swiftpm?

Comment by Ian Ynda-Hummel (JIRA)

I was literally coming back to this today. I don't immediately see a connection to spm.

The connection I see is that it might be easier to support one single way to run unit tests on all platforms with SwiftPM.

Different thought: the fact that we still have to `bridge()` standard library value types means that quite a few tests that use that temporary method will not compile under Darwin Foundation. Perhaps we could provide a dummy bridge function for that platform.

Comment by Ian Ynda-Hummel (JIRA)

Yeah. I remember having to create an extension that defines them manually.

That said, the problem I'm actually running into right now is that I am having trouble getting a new target to not pick up CoreFoundation headers from multiple places. It seems that linking OS X's Foundation is just conflicting a bunch with heads being pulled in from... somewhere for Swift Foundation's version of CF.

Comment by Ian Ynda-Hummel (JIRA)

I feel like I'm going a little crazy. It seems like the Foundation that ships with the current Xcode beta is incompatible with the current swift toolchain. I've tried the current preview in the Xcode beta and a couple of the nightlies from swiftnightly.com. It seems to stem from the use of

Comment by Ian Ynda-Hummel (JIRA)

Using the newest official snapshot it still fails to build the CoreFoundation module:

/Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFNotificationCenter.h:14:39: Expected ';' after top level declarator

There is now a DarwinCompatibilityTests Xcode project in the swift-corelibs-foundation repository that builds the tests against native Foundation. Whilst many of the tests still fail this does allow the tests to be run using Xcode's XCTest runner.