[vlc-devel] [PATCH] AudioQueue aout (for the Apple iOS)

Pierre d'Herbemont pdherbemont at free.fr
Mon Sep 13 11:03:23 CEST 2010

On Sun, Sep 12, 2010 at 2:01 PM, Jean-Baptiste Kempf <jb at videolan.org> wrote:

> About MobileVLC, I have mixed feelings...
> In fact, the MobileVLC could go in vlc.git/projects/macosx
> or in a
> separate repo... But people getting the VLC sources, would expect to
> have the iOS "VLC" too.

I would like to push MobileVLC as a premium client of libvlc. This
would potentially allow us to test/use/improve libvlc with a real
world client. Having it out-of-tree is an emphasis in this direction
in my opinion. Also, we had MobileVLC in a separate git, because it
looked like the simplest and cleanest approach at that time.

Now, if you really want to have it in projects/ - the cool thing is -
this is absolutely possible. That's the great thing about clean
layering :-)

However, I think it's great to have a separate repo. In the end the
main repo won't be bloated. But the real point is version numbering
and releases. MobileVLC has a different version numbering. And I think
it make little sense to adjust MobileVLC releases with regular VLC
releases. For a start, the first release of MobileVLC is happening
now. When vlc.git is in a flux. Then, the next release will contain
MobileVLC specific features, in a middle of a VLC code freeze
eventually. etc.

> This question is a bit broader than just the iOS, but applies also for
> Maemo/MeeGo/WinCE/WebOS Qt VLC program. Where should we put it?

If you plan to this on top of libvlc, projects/ or separate repo,
depends on the planned release cycle. If this is done as a module,
this should go in modules/gui, but then you are stuck with the same
release cycle.


More information about the vlc-devel mailing list