spelling/grammar/wording
Originally committed as revision 4589 to svn://svn.ffmpeg.org/ffmpeg/trunk
This commit is contained in:
parent
291dcdb356
commit
e180129f63
30
doc/faq.texi
30
doc/faq.texi
@ -182,25 +182,25 @@ The build process creates ffmpeg_g, ffplay_g, etc. which contain full debug
|
|||||||
information. Those binaries are strip'd to create ffmpeg, ffplay, etc. If
|
information. Those binaries are strip'd to create ffmpeg, ffplay, etc. If
|
||||||
you need the debug information, used the *_g versions.
|
you need the debug information, used the *_g versions.
|
||||||
|
|
||||||
@section I do not like the LGPL, can I contribute code under the GPL instead
|
@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
|
Yes, as long as the code is optional and can easily and cleanly be placed
|
||||||
#ifdef CONFIG_GPL without breaking anythng, so for example
|
under #ifdef CONFIG_GPL without breaking anything. So for example a new codec
|
||||||
a new codec or filter would be ok under GPL while a bugfix to LGPL code wont
|
or filter would be OK under GPL while a bugfix to LGPL code would not.
|
||||||
|
|
||||||
@section I want to compile xyz.c alone but my compier produced many errors
|
@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
|
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
|
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
|
the whole libav*. If you wish, disable some parts with configure switches.
|
||||||
switches, you can also try to hack it and remove more but if you seriously
|
You can also try to hack it and remove more, but if you had problems fixing
|
||||||
wanted to ask the question above then you are not qualified for this
|
the compilation failure then you are probably not qualified for this.
|
||||||
|
|
||||||
@section visual c++ produced many errors
|
@section Visual c++ produces many errors.
|
||||||
|
|
||||||
you need a c compiler (visual c++ is not compliant to the c standard)
|
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
|
If you wish - for whatever weird reason - to use visual C++ for your
|
||||||
then you can link the visual c++ code with libav* as long as you compile
|
project then you can link the visual C++ code with libav* as long as
|
||||||
the later with a working c compiler
|
you compile the latter with a working C compiler.
|
||||||
|
|
||||||
@bye
|
@bye
|
||||||
|
Loading…
x
Reference in New Issue
Block a user