[swift-evolution] Swift 4: Support for static libs / modular development.
k at keith.so
Thu May 11 15:27:51 CDT 2017
Until we have native support for this in Xcode (or some sort of SwiftPM
integration that would help with this), I found a workaround to allow
you to trick Xcode into building static frameworks, so you can sidestep
the dynamic framework issues.
You can find it here: https://github.com/keith/swift-staticlibs
On Thu, Mar 9, 2017, at 10:34, Jacek Suliga via swift-evolution wrote:
> I'd like to add a +1 for this request/discussion starter.
> We're on the same boat, with 70+ dynamic libraries, facing the same
> challenges as Raphael mentioned.>
> Jacek Suliga | Flagship Infra
> On Fri, Feb 17, 2017 at 10:02 AM, Raphael Sebbe via swift-evolution
> <swift-evolution at swift.org> wrote:>> Sure, thank you. If SwiftPM gets a working integration in Xcode 9,
>> that could do it.>>
>> On Fri, Feb 17, 2017 at 1:50 PM Ole Begemann <ole at oleb.net> wrote:
>>> > On 17 Feb 2017, at 10:28, Raphael Sebbe via swift-evolution <swift-
>>> > evolution at swift.org> wrote:>>> >
>>> > I'm not fully aware of the state of discussion, so sorry if it is
>>> > already being addressed. I wanted to bring some feedback and
>>> > awareness about the need of a supported way to build app
>>> > components as *static libraries* in Swift.>>>
>>> Part of the recently accepted (for Swift 4) SE-0146 "Package
>>> Manager Product Definitions"  is support for static library
>>> products in the Swift Package Manager.>>>
>>> SwiftPM is not Xcode, of course. I just thought I'd mention it.
>>> : https://github.com/apple/swift-evolution/blob/master/proposals/0146-package-manager-product-definitions.md>>>
>> swift-evolution mailing list
>> swift-evolution at swift.org
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution