> 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 compilation like linker scripts and t
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 compilation like linker scripts and tacked on assembly data
segments. I am not certain those edge use cases are supported yet.
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 (ab
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
> Darwin platforms,
> - swift
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 evol
