Re: [swift-corelibs-dev] Objective-C Foundation vs CoreLibs Foundation

> On May 23, 2016, at 3:34 PM, Philippe Hausler via swift-corelibs-dev > wrote: > > There are a few considerations for the package manager: we may have circular > build requirements, swift-corelibs-foundation does some squirrelly things > with linking and

Re: [swift-corelibs-dev] Objective-C Foundation vs CoreLibs Foundation

Would you agree that the first step should be to have the project as a SwiftPM package so that we have a more consistent way to run tests on all platforms? Do you know if SwiftPM is far enough to support swift-corelibs-foundation? I might have a go at it once I finish implementing NSProgress

Re: [swift-corelibs-dev] Objective-C Foundation vs CoreLibs Foundation

Hi David, > On May 22, 2016, at 8:15 AM, David Hart via swift-corelibs-dev > wrote: > > Hello, > > The discussion we had previously on this mailing list made it quite clear > that: > > - Objective-C Foundation is the framework that is supposed to be used on all

[swift-corelibs-dev] Objective-C Foundation vs CoreLibs Foundation

Hello, The discussion we had previously on this mailing list made it quite clear that: - Objective-C Foundation is the framework that is supposed to be used on all Darwin platforms, - swift-corelibs-foundation will be the Foundation framework for all other platforms, - Both frameworks will