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-st
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@swift.org> wrote:
> S
Sure, thank you. If SwiftPM gets a working integration in Xcode 9, that
could do it.
Raphael
On Fri, Feb 17, 2017 at 1:50 PM Ole Begemann wrote:
>
> > On 17 Feb 2017, at 10:28, Raphael Sebbe via swift-evolution <
> swift-evolution@swift.org> wrote:
> >
> > I'm not fully aware of the state of di
> On 17 Feb 2017, at 10:28, Raphael Sebbe via swift-evolution
> 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 librarie
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.
We've moved most of our new developments to Swift 3. Our apps are compl
