[Ffmpeg-devel] [PATCH] small build cleanup + new configure option
Gildas Bazin
gbazin
Sat Jan 21 11:13:07 CET 2006
On Friday 20 January 2006 20:33, Diego Biurrun wrote:
> On Fri, Jan 20, 2006 at 07:43:32PM +0000, Gildas Bazin wrote:
> > On Thursday 19 January 2006 22:22, Diego Biurrun wrote:
> > > On Thu, Jan 19, 2006 at 08:18:12PM +0000, Gildas Bazin wrote:
> > > >
> > > > --- libavformat/Makefile 16 Jan 2006 14:59:54 -0000 1.109
> > > > +++ libavformat/Makefile 19 Jan 2006 20:10:16 -0000
> > > > @@ -32,8 +39,6 @@
> > > >
> > > > -# file I/O
> > > > -OBJS+= avio.o aviobuf.o file.o
> > > > OBJS+= framehook.o
> > > >
> > > > @@ -62,6 +67,11 @@
> > > >
> > > > +# protocols I/O
> > > > +OBJS+= avio.o aviobuf.o
> > > > +
> > > > +ifeq ($(CONFIG_PROTOCOLS),yes)
> > > > +OBJS+= file.o
> > > > ifeq ($(CONFIG_NETWORK),yes)
> > > > OBJS+= udp.o tcp.o http.o rtsp.o rtp.o rtpproto.o
> > >
> > > Why is file.o in CONFIG_PROTOCOLS, while avio.o and aviobuf.o are not?
> >
> > avio.o and aviobuf.o provide things like put_byte(), etc... which are
used
> > by muxers for instance.
>
> So why is file.o in #ifdef CONFIG_PROTOCOLS?
>
Because file.c provides 1 of the protocols implementation.
avio.o/aviobuf.o are not protocols themselves but a higher level API around
the protocols (put_byte(), etc...).
--
Gildas
More information about the ffmpeg-devel
mailing list