Skip to content
Snippets Groups Projects
Commit e867d9b9 authored by Diego Biurrun's avatar Diego Biurrun
Browse files

Update gcc sections. 

Originally committed as revision 7712 to svn://svn.ffmpeg.org/ffmpeg/trunk
parent b5bfb9f9
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 4 additions and 6 deletions
doc/faq.texi
+ 4
− 6
View file @ e867d9b9
...@@ -257,9 +257,9 @@ already incorporate ffmpeg at (@url{projects.php}). ...@@ -257,9 +257,9 @@ already incorporate ffmpeg at (@url{projects.php}).
@section Can you support my C compiler XXX ? @section Can you support my C compiler XXX ?
No. Only GCC is supported. GCC is ported to most systems available and there It depends. If your compiler is C99-compliant, then patches to support
is no need to pollute the source code with @code{#ifdef}s it are likely to be welcome if they do not pollute the source code
related to the compiler. with @code{#ifdef}s related to the compiler.
@section Can I use FFmpeg or libavcodec under Windows ? @section Can I use FFmpeg or libavcodec under Windows ?
...@@ -270,9 +270,7 @@ sections in the FFmpeg documentation to find more information. ...@@ -270,9 +270,7 @@ sections in the FFmpeg documentation to find more information.
@section Can you add automake, libtool or autoconf support ? @section Can you add automake, libtool or autoconf support ?
No. These tools are too bloated and they complicate the build. Moreover, No. These tools are too bloated and they complicate the build.
since only @samp{gcc} is supported they would add little advantages in
terms of portability.
@section Why not rewrite ffmpeg in object-oriented C++ ? @section Why not rewrite ffmpeg in object-oriented C++ ?
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment