Commit 086a7299 authored by Marius Rackwitz's avatar Marius Rackwitz

[Changelog] Stylistic improvements

Thanks @segiddins.
parent 5ef969a3
...@@ -8,24 +8,25 @@ To install release candidates run `[sudo] gem install cocoapods --pre` ...@@ -8,24 +8,25 @@ To install release candidates run `[sudo] gem install cocoapods --pre`
##### Highlighted Enhancement That Needs Testing ##### Highlighted Enhancement That Needs Testing
* Support Frameworks & Swift: This allows to build podspecs, which contain Swift * Support Frameworks & Swift: This allows the creation of pods that contain Swift.
code, because it now automatically recognize Swift source files and determines CocoaPods now recognizes Swift source files and builds dynamic frameworks when
if it is required to build a framework. As soon as a project explicitly necessary.
opts-in to `use_frameworks!` in the Podfile or if any dependency contains As soon as a project explicitly opts-in to `use_frameworks!` in the Podfile, or
Swift, the pods will be integrated as frameworks. if any dependency contains Swift, all pods for that target will be integrated
As pod author you can change the name of the built framework, by specifying as frameworks.
As a pod author, you can change the name of the built framework by specifying a
`module_name` in the podspec. The built frameworks are embedded into the host `module_name` in the podspec. The built frameworks are embedded into the host
application with a new shell script build phase in the user project to allow application with a new shell script build phase in the user project to allow
configuration-dependent pods. for configuration-dependent pods.
[Marius Rackwitz](https://github.com/mrackwitz) [Marius Rackwitz](https://github.com/mrackwitz)
[#2835](https://github.com/CocoaPods/CocoaPods/issues/2835) [#2835](https://github.com/CocoaPods/CocoaPods/issues/2835)
##### Breaking ##### Breaking
* Bundle Resources into Frameworks: Previously all resources were compiled and * Bundle Resources into Frameworks: Previously all resources were compiled and
copied into the `mainBundle`. By now Pods have to use copied into the `mainBundle`. Now Pods have to use
`[NSBundle bundleForClass:<#Class from Pod#>]` to access provided resources `[NSBundle bundleForClass:<#Class from Pod#>]` to access provided resources
relatively to the bundle. relative to the bundle.
[Boris Bügling](https://github.com/neonichu) [Boris Bügling](https://github.com/neonichu)
[#2835](https://github.com/CocoaPods/CocoaPods/issues/2730) [#2835](https://github.com/CocoaPods/CocoaPods/issues/2730)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment