<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38">
<TITLE>RE: [vlc-devel] commit: Document filter chain API. (Jean-Paul Saman)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Doxygen is built from doc. cd into the dir and run doxygen AFAIK.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: vlc-devel-bounces@videolan.org on behalf of Rémi Denis-Courmont<BR>
Sent: Mon 8/11/2008 2:19 PM<BR>
To: Mailing list for VLC media player developers<BR>
Subject: Re: [vlc-devel] commit: Document filter chain API. (Jean-Paul Saman)<BR>
<BR>
<BR>
On Mon, 11 Aug 2008 13:37:28 +0200 (CEST), git@videolan.org (git version<BR>
control) wrote:<BR>
> vlc | branch: master | Jean-Paul Saman <jpsaman@videolan.org> | Mon Aug<BR>
11<BR>
> 17:21:25 2008 +0800| [def14b82467447f3f7fd1717d237e99837d11de9] |<BR>
> committer: Jean-Paul Saman<BR>
><BR>
> Document filter chain API.<BR>
<BR>
Where how is the Doxygen documentation built? I do not understand why some<BR>
files seem to be parsed for documentation and others not.<BR>
<BR>
--<BR>
Rémi Denis-Courmont<BR>
<BR>
_______________________________________________<BR>
vlc-devel mailing list<BR>
To unsubscribe or modify your subscription options:<BR>
<A HREF="http://mailman.videolan.org/listinfo/vlc-devel">http://mailman.videolan.org/listinfo/vlc-devel</A><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>