aboutsummaryrefslogtreecommitdiffstats
path: root/doc/faq.texi
diff options
context:
space:
mode:
authorMartin Boehme <boehme@inb.uni-luebeck.de>2005-09-28 21:18:11 +0000
committerDiego Biurrun <diego@biurrun.de>2005-09-28 21:18:11 +0000
commitbe0efc0cfa04964ae0373d42fadfe727ec476919 (patch)
tree0599e0afa3cd2a16f7c1ae51e5943ee86d40951e /doc/faq.texi
parent515875484bc70477cba4e5c4a0f535751dff3213 (diff)
downloadffmpeg-be0efc0cfa04964ae0373d42fadfe727ec476919.tar.gz
Since there have been quite a few questions recently on how to use the
FFmpeg libraries with Visual C++, here's a patch for the documentation that explains everything in (excruciating) detail. patch by Martin Boehme <boehme -- at -- inb -- dot -- uni-luebeck -- dot -- de> Originally committed as revision 4620 to svn://svn.ffmpeg.org/ffmpeg/trunk
Diffstat (limited to 'doc/faq.texi')
-rw-r--r--doc/faq.texi7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/faq.texi b/doc/faq.texi
index 438f5e646f..fc708c1fd1 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -160,8 +160,8 @@ related to the compiler.
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 find more information.
+@emph{Native Windows Compilation} and @emph{Visual C++ compatibility}
+sections in the FFmpeg documentation to find more information.
@section Can you add automake, libtool or autoconf support ?
@@ -201,6 +201,7 @@ the compilation failure then you are probably not qualified for this.
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.
+you compile the latter with a working C compiler. For more information, see
+the @emph{Visual C++ compatibility} section in the FFmpeg documentation.
@bye