Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Change issue status back to 'Assigned'
Pending code changes (auto-populated)
Select items in the list
Operating system. [ID: 1339385]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
#1However the static library framework has compatibility issues with CocoaPods when also mixing in dynamic frameworks -- see
iOS 8 and above supports dynamic-library frameworks in application code for both Obj-C and Swift; in theory building libvpx to a dynamic library in the VPX.framework should fix the potential linking issues when mixing with other dynamic libs in CocoaPods.
For backwards-compatibility for iOS 6/7 builds, this should probably be an option on the build script.
I'll see if I can whip up a patch...