Add Cocoapods static_framework support #176
Conversation
| @@ -6,7 +6,7 @@ | |||
| // software distributed under the License is distributed on an "AS IS" BASIS, | |||
| // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | |||
|
|
|||
| import ObjectiveC | |||
| import Foundation | |||
There was a problem hiding this comment.
Replaced because of using NSNumber here. Had compile errors without that.
|
Hi @soniccat ! Can you please link me to some documentation for this Also, is this something that should be determined by those entities that import LayoutKit rather than by LayoutKit itself? |
|
@staguer hi, here it is http://blog.cocoapods.org/CocoaPods-1.4.0/ I see they have written it recently can't say about dependencies, need to read the doc, it seems setting the flag should be enough, at least I've tested that it works |
|
Lgtm based on reading doc. Any downsides? |
|
Enabling this will cause the binary to be linked statically. If the pod consumer has multiple targets using LayoutKit, LayoutKit will be liked multiple times. Agree with @staguer it might be more appropriate for the consumers to decide how it will be linked. Cocoapods 1.5.0 is adding support for this use case, FYI. |
I see Cocoapods RC (1.4.0.rc.1) supports swift static frameworks. Added that to avoid creating a dynamic library.
The latest Cocoapods RC can be installed using this command
sudo gem install cocoapods --pre