5 ms·
Does the move to LGPLv2.1+ for libVLC, libVLCcore and libcompat allow for Applidium's VLC iPhone port (http://applidium.com/en/applications/vlc http://applidium
by chrisballinger 15y ago
Does the move to LGPLv2.1+ for libVLC, libVLCcore and libcompat allow for Applidium's VLC iPhone port (http://applidium.com/en/applications/vlc http://applidium.com/en/applications/vlc) to be resubmitted to the App Store after some minor changes?
- tcas 15y agoI don't think so. According to the FAQ they don't think it'll change (http://www.videolan.org/press/lgpl-libvlc.html http://www.videolan.org/press/lgpl-libvlc.html). The LGPL requires dynamically linking the library or providing the raw object files if statically linked to allow the end user to change the LGPL library in the code. I've read that the app store's code signing + pay wall to get a signing certificate violates this exception, so it looks like a no go. It would have been nice if they added in a static linking exception. Hopefully this will allow for other open source software to link to libVLC without having to fully upgrade to GPL however.
- dtorres 15y agoEven if it's not available in the App Store, you can get it here: http://www.videolan.org/vlc/download-ios.html http://www.videolan.org/vlc/download-ios.html
- jbk 15y agoYes/No. We also need to move many VLC modules to LGPL, since VLC/iOS needs static linking on this platform. But, I am working on it. It takes a lot of time, and I am already doing much on my free time.