You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I imagine this will be one for @lukeredpath principally, but if others have opinions then please jump in.
Also, as a preface, I'm not massively familiar with the implications of changing the targets in libPusher from being static libraries to dynamic frameworks.
When looking into adding tvOS support I discovered that while SocketRocket supports it, ReactiveCocoa only added support for it in 4.0.0 (tangentially related: Reachability has support for it on master but 3.2, the latest release, doesn't have support for it).
However, upgrading ReactiveCocoa to 4.0.0 means that it becomes a framework and contains Swift code (targeting iOS 8.0+).
As such, what do you think about changing libPusher to build frameworks instead of static libraries and, as a consequence, target iOS 8.0+?
The text was updated successfully, but these errors were encountered:
I imagine this will be one for @lukeredpath principally, but if others have opinions then please jump in.
Also, as a preface, I'm not massively familiar with the implications of changing the targets in libPusher from being static libraries to dynamic frameworks.
When looking into adding tvOS support I discovered that while SocketRocket supports it, ReactiveCocoa only added support for it in 4.0.0 (tangentially related: Reachability has support for it on master but 3.2, the latest release, doesn't have support for it).
However, upgrading ReactiveCocoa to 4.0.0 means that it becomes a framework and contains Swift code (targeting iOS 8.0+).
As such, what do you think about changing libPusher to build frameworks instead of static libraries and, as a consequence, target iOS 8.0+?
The text was updated successfully, but these errors were encountered: