MobileVLCKit in iOS app - license and project settings

[SerJ_G]

Hello,

I'm working on iOS application that will use MobileVLCKit framework in it. I have several question about using it in iOS applications development and distributing to Apple Appstore confirming its LGPL v2.1 license.

What I've already done:
I created my test project with proper configuration, downloaded MobileVLCKit from http://code.videolan.org/videolan/VLCKit.git and executed ./buildMobileVLCKit.sh script. Then I've added "MobileVLCKit.xcodeproj" as subproject to my application and done next changes to my xcode project in build phases:

• Added "MobileVLCKit" and "DynamicMobileVLCKit" to "Target dependencies"
• Added "DynamicMobileVLCKit" to "Link Binary With Libraries"
• Added "DynamicMobileVLCKit.framework" in "Copy Files"

I build my project and everything works for me as expected.

But then I start investigate MobileVLCKit license LGPL 2.1 and articles about using it in iOS projects. The more I read, the more I'm getting confused if it is allowed to use it for iOS project that is going to be published in Apple's AppStore.

I have next questions:
1. Can I publish to AppStore free app that is using MobileVLCKit with LGPL 2.1 license? If yes, what I should do to achieve that?
e.g. How should I setup my project? Should I publish all my projects source code public?
2. The same question for paid app on AppStore.

P.S.
Sorry, if my question is kinda newbie, I'm not familiar with licenses. But I highly respect all developers that contributed to VLC project and want use their work properly without violating any rules.

[bubu?]

Hello,

Have a read here
I believe that it should answer yours questions.

Cheers,

[SerJ_G]

Thank you, Bubu?!

According to this

Anything statically linked to the library can only be redistributed under LGPL, but applications that use the library don't have to be. You must allow reverse engineering of your application as necessary to debug and relink the library.

and

Disclose Source
If the software is statically linked (i.e. compiled into) your work, you must release object code or source code such that the user can modify the library. If otherwise (dynamically linked), you must make the source for the library available.

all iOS apps that are using framework with LGPL 2.1, in our case MobileVLCKit, should provide all source code publicly, am i right?

[Jean-Baptiste Kempf]

Yes, and that should be fine, if you use dynamic ones.