[Ffmpeg-cvslog] CVS: ffmpeg/doc faq.texi,1.18,1.19

Michel Bardiaux mbardiaux
Mon Sep 12 15:48:06 CEST 2005


Michael Niedermayer CVS wrote:
> Update of /cvsroot/ffmpeg/ffmpeg/doc
> In directory mail:/var2/tmp/cvs-serv17915
> 
> Modified Files:
> 	faq.texi 
> Log Message:
> common questions people ask me all the time, lets hope this reduces the stuff in my inbox, otherwise ill train bogofilter on them ...
> 
> 
> Index: faq.texi
> ===================================================================
> RCS file: /cvsroot/ffmpeg/ffmpeg/doc/faq.texi,v
> retrieving revision 1.18
> retrieving revision 1.19
> diff -u -d -r1.18 -r1.19
> --- faq.texi	9 Jun 2005 19:54:58 -0000	1.18
> +++ faq.texi	11 Sep 2005 16:39:47 -0000	1.19
> @@ -182,4 +182,25 @@
>  information. Those binaries are strip'd to create ffmpeg, ffplay, etc. If
>  you need the debug information, used the *_g versions.
>  
> + at section I do not like the LGPL, can I contribute code under the GPL instead
> +
> +yes, ffmpeg contains GPL and LGPL code, the GPL code is only compiled if
> +'--enable-gpl' is passed to configure in which case the resulting binary will
> +be covered by the GPL instead of the LGPL

I object rather strongly to this. If patches under GPL are accepted, 
very soon all of ffmpeg will effectively be GPL. I cant believe this is 
the official policy.

> +
> + at section I want to compile xyz.c alone but my compier produced many errors
> +
> +common code is in its own files in libav* and is used by the individual
> +codecs, they will not work without the common parts, you have to compile
> +the whole libav* and if you wish disable some parts with configure
> +switches, you can also try to hack it and remove more but if you seriously
> +wanted to ask the question above then you are not qualified for this
> +
> + at section visual c++ produced many errors
> +
> +you need a c compiler (visual c++ is not compliant to the c standard)

That is not exactly true. vc++ is compliant with C89. It is not 
compliant with the subset of C9x that lavc requires. Is even gcc itself 
100% C9x compliant now?

> +if you wish for whatever weird 

'weird' is a matter of opinion.

> reason use visual c++ for your project
> +then you can link the visual c++ code with libav* as long as you compile
> +the later with a working c compiler
^^^^^^^latter
> +
>  @bye
> 


-- 
Michel Bardiaux
R&D Director
T +32 [0] 2 790 29 41
F +32 [0] 2 790 29 02
E mailto:mbardiaux at mediaxim.be

Mediaxim NV/SA
Vorstlaan 191 Boulevard du Souverain
Brussel 1160 Bruxelles
http://www.mediaxim.com/





More information about the ffmpeg-cvslog mailing list