[Ffmpeg-cvslog] CVS: ffmpeg/doc faq.texi,1.20,1.21
Diego Biurrun CVS
Mon Sep 12 17:51:31 CEST 2005
Update of /cvsroot/ffmpeg/ffmpeg/doc
In directory mail:/var2/tmp/cvs-serv9169
RCS file: /cvsroot/ffmpeg/ffmpeg/doc/faq.texi,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -d -r1.20 -r1.21
--- faq.texi 12 Sep 2005 15:16:27 -0000 1.20
+++ faq.texi 12 Sep 2005 15:51:29 -0000 1.21
@@ -182,25 +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
+ at section I do not like the LGPL, can I contribute code under the GPL instead ?
-yes, as long as the code is optional and can easily and cleanly be placed under
-#ifdef CONFIG_GPL without breaking anythng, so for example
-a new codec or filter would be ok under GPL while a bugfix to LGPL code wont
+Yes, as long as the code is optional and can easily and cleanly be placed
+under #ifdef CONFIG_GPL without breaking anything. So for example a new codec
+or filter would be OK under GPL while a bugfix to LGPL code would not.
- at section I want to compile xyz.c alone but my compier produced many errors
+ at section I want to compile xyz.c alone but my compiler 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
+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*. If you wish, disable some parts with configure switches.
+You can also try to hack it and remove more, but if you had problems fixing
+the compilation failure then you are probably not qualified for this.
- at section visual c++ produced many errors
+ at section Visual c++ produces many errors.
-you need a c compiler (visual c++ is not compliant to the c standard)
-if you wish for whatever weird 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
+You need a C compiler (visual C++ is not compliant to the C standard).
+If you wish - for whatever weird reason - to use visual C++ for your
+project then you can link the visual C++ code with libav* as long as
+you compile the latter with a working C compiler.
More information about the ffmpeg-cvslog