iOS, Frameworks that use WebRTC.Framework

[Rajeev Tipnis]

- We have our own framework that we share with our customers to use.

- We are working on adding iOS WebRTC.Framework to this framework of ours

We need bitcode support, so have built this Framework like this:

https://webrtc.org/native-code/ios/

python build_ios_libs.py --bitcode

We have a few different ways of providing these frameworks to be used by our customers:

Option #1: Build a separate ".a" static library instead of WebRTC.Framework, link it with our Framework and then have the customers use our Framework

Option #2: Include WebRTC.Framework inside our Framework but also provide WebRTC.Framework to our customers and let them include both these Frameworks

the top answer here has details: https://stackoverflow.com/questions/34681435/how-to-add-a-framework-inside-another-framework-umbrella-framework

Option #3: Umbrella Frameworks

This is not something one should do (not a good practice, Apple does not recommend it). The same article above provides the reasons. However, this is also an option.

--------

We will not use Option #3

However, between Option #1 and #2, we are leaning toward Option #2, as seems like the most reliable approach (Option #1 currently is giving us some run-time errors).

I'd love to get feedback and comments on our choice. Specifically, does anyone know if the final applications being built with Option #2 are going to be kosher from Apple's appstore guidelines perspective? 

Hoping they are not going to reject the final apps that are built this way.

Thanks in advance. 

[Krishna Thakur]

Hi Rajeev, 

I was trying to get a static library from WebRTC.framwrok  using "lipo WebRTC -thin x_64 -output libwebrtc.a", but the problem here is when i am including headers in build settings. I am getting this error : "Include of non-modular header inside framework module".

Any idea?