LGPL Licence requirements for iOS MobileVLCKit.framework

[Mikhail Kolesov]

Hello,
I'm working on iOS app which streams 4K video. I'm looking at alternative video players (in opposite to AVPlayer). MobileVLCKit.framework works well in this case but my customer worries about possible hidden problems with LGPL licence. The main source of app is closed and cannot be opened. So the questions are:

1. I use MobileVLCKit.framework (without any changes) as Embedded binary in Xcode, so it's copied and placed separately inside iOS bundle. Is it correct that in this way I use MobileVLCKit.framework as dynamic library and according to LGPL I do not have to disclose any source of my app?

2. Should I put some info into app UI, about using of MobileVLCKit.framework? Is it like About VLC screen in "VLC for iOS" app?

3. Should I put some info somewhere else, for example at the related website? Like it's made by GoPro (https://gopro.com/help/articles/block/O ... e-Software)

4. Is it correct that any source changes of MobileVLCKit.framework should be published somewhere, for example at the related website, again like GoPro link?

PS: It's my first experience with open source licences so I appreciate any feedback on it. Thank you, in advance.

-Mikhail

[Jean-Baptiste Kempf]

1. I use MobileVLCKit.framework (without any changes) as Embedded binary in Xcode, so it's copied and placed separately inside iOS bundle. Is it correct that in this way I use MobileVLCKit.framework as dynamic library and according to LGPL I do not have to disclose any source of my app?

Yes, this is correct. No extra disclosure needed.

(btw, did you change something to get the Framework as dynamic?

2. Should I put some info into app UI, about using of MobileVLCKit.framework? Is it like About VLC screen in "VLC for iOS" app?

It is debatable, but I'd argue you should, in a about screen.

3. Should I put some info somewhere else, for example at the related website? Like it's made by GoPro (https://gopro.com/help/articles/block/O ... e-Software)

I don't think this is needed, but this would be appreciated.

4. Is it correct that any source changes of MobileVLCKit.framework should be published somewhere, for example at the related website, again like GoPro link?

Yes. You could even send them back to us

[Mikhail Kolesov]

Thanks for your reply!

I did not change anything to get the framework dynamic. For dynamic here I mean that the library binary code is placed in a separate folder called Frameworks (inside app bundle). And the the library binary is not appended to the main app in this case. This feature is available if you add a framework in "General/Embedded binaries" section of Xcode project. As I understand the frameworks from app bundle internal Frameworks folder are loaded separately.
There is a dylib type (i.e for swift libraries) for "true" dll, but it's not available for the 3rd party developers as we are.