When we were first bringing up the project we had a hack that forced the compiler to do incremental builds of the Swift files. However, it turned out that it wasn’t really safe or supported.
If there is some way to actually turn that on now in a way that allows quick turnaround (probably sacrificing things like whole module optimization and stuff), I would be in favor of enabling it. - Tony > On Jan 30, 2017, at 4:49 PM, Robert F Dickerson via swift-corelibs-dev > <swift-corelibs-dev@swift.org> wrote: > > This has probably been discussed in the past, but wanted to revisit the idea > of using native Swift tools to build Foundation. I brought this up in the > Slack group, and it seemed to be warmly received- although probably still not > simple because of some cyclical dependency issues in the build process. > > But, I think that there would be a lot of value in being able to build > Foundation (and CoreFoundation) only using SwiftPM, in other words, simply > with `swift build`. > > Now that SwiftPM is improving its ability to pass in compilation flags more > easily and C module compilation. I think that the project could be > restructured to make this work. What would be the obstacles for getting this > working? > > > _______________________________________________ > swift-corelibs-dev mailing list > swift-corelibs-dev@swift.org > https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
_______________________________________________ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
