summaryrefslogtreecommitdiff
path: root/doc/faq.texi
diff options
context:
space:
mode:
authorFabrice Bellard <fabrice@bellard.org>2003-09-16 20:28:18 +0000
committerFabrice Bellard <fabrice@bellard.org>2003-09-16 20:28:18 +0000
commit988a9f9e3a47e2b9b6459ad8d982e43bfeae52d1 (patch)
tree6fb98486b95407b220d2c1b88cb58647afb5f3eb /doc/faq.texi
parent211f2123c53a140009ce6c1abe4a513aaf8f4645 (diff)
doc update
Originally committed as revision 2285 to svn://svn.ffmpeg.org/ffmpeg/trunk
Diffstat (limited to 'doc/faq.texi')
-rw-r--r--doc/faq.texi9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/faq.texi b/doc/faq.texi
index e85a29deb2..8e8198d851 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -69,11 +69,12 @@ No. Only GCC is supported. GCC is ported on most systems available and I
don't see the need to pollute the source code with @code{#ifdef}s
related to the compiler.
-@section I want to use ffmpeg or libavcodec under Windows. Can you support my proprietary C compiler XXX ?
+@section Can I use FFmpeg or libavcodec under Windows ?
-No. Use @code{mingw-gcc} available at @url{http://www.mingw.org/} to
-compile the code. It generates object files fully compatible with other
-windows compilers.
+Yes, but the MinGW tools @emph{must} be used to compile FFmpeg. You
+can link the resulting DLLs with any other Windows program. Read the
+@emph{Native Windows Compilation} section in the FFmpeg documentation
+to have more information.
@section Can you add automake, libtool or autoconf support ?