[vlc-devel] Re: VLC as a library rather than an application ?
sigmunau at stud.ntnu.no
Wed Jun 18 14:15:42 CEST 2003
The codebase of vlc is essencially divided in three parts: A library called
libvlc that is >90% of the code. The vlc application that uses libvlc, and a
mozilla plugin that uses libvlc.
The unfortunate part is that libvlc is quite specific to vlc, and does not
have a very generic interface, and people that have tried to build other
apps based on it have had problems in the past.
have a look at src/vlc.c in the source tarball to see how vlc uses libvlc,
and include/vlc/vlc.h to see the programming interface of libvlc
On Wed, Jun 18, 2003 at 01:56:17PM +0200, kktos wrote:
> The VideoLan Client is a whole application.
> But let's say I want to write an application, a MP3/WAV player. I wish to use the videolan tools for the broadcast.
> So is there a way to have the client as a library of functions to call instead of the whole app ?
> I'm not sure it's interesting but I'm on windows.
This is the vlc-devel mailing-list, see http://www.videolan.org/vlc/
To unsubscribe, please read http://developers.videolan.org/lists.html
If you are in trouble, please contact <postmaster at videolan.org>
More information about the vlc-devel