virtualenv/FFmpeg
1
0
Fork 0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2024-12-23 12:43:46 +02:00
Code Issues Releases Activity

common questions people ask me all the time, lets hope this reduces the stuff in my inbox, otherwise ill train bogofilter on them ...

Browse Source 
Originally committed as revision 4583 to svn://svn.ffmpeg.org/ffmpeg/trunk
This commit is contained in:
Michael Niedermayer 2005-09-11 16:39:47 +00:00
parent c44a131dc7
commit 61a1e08156
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
doc/faq.texi
View File

@ -182,4 +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
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
@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
@section visual c++ produced 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
@bye @bye