[swift-corelibs-dev] Migrate corelibs-foundation to the newest APIs
As you know, currently, as of the 03-24 DEVELOPMENT snapshot, the function
signatures for Foundation has diverged. This has caused us to create
platform specific calls to the NSString, NSDate, NSCache, etc. classes. For
instance,
#if os
(Linux)
|let lastSlash = fileName.rangeOfString("/", options:
|NSStringCompareOptions.BackwardsSearch)
|#else
|let lastSlash = fileName.range(of: "/", options:
|NSStringCompareOptions.backwardsSearch)
|#endif
I was curious about the timeline for the migration to the newer APIs and
whether someone in particular was working on it. We have some developers
here at IBM@Swift that could do some of this work, but want to make sure we
aren't duplicating work and are coordinated.
___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
[swift-corelibs-dev] Building Foundation on Linux with incremental builds?
Does anyone know how to compile Foundation (with Ninja) on Ubuntu Linux 16.04 with Incremental builds enabled? It currently takes over 4 min on my 8 core, 16 GB machine because it rebuilds the project from the beginning each time. Any way to make the development to test cycle faster would be appreciated! I have inspected the build.ninja file and it seems to be fine, however running `ninja` or `ninja test` will rebuild the entire project. In other words, when I make one line of code to URLSession.swift, it ends up rebuilding NSCharacterSet.swift and NSPersonNameComponents.swift, etc. Over 100 source files before building URLSession.swift and finally linking libFoundation.so. ___ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
[swift-corelibs-dev] Building Foundation with SwiftPM
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
