diff options
| author | Diego Biurrun <diego@biurrun.de> | 2005-12-02 15:25:10 +0000 |
|---|---|---|
| committer | Diego Biurrun <diego@biurrun.de> | 2005-12-02 15:25:10 +0000 |
| commit | 5062c60c184030e3a8d87046ff7442647cbceaee (patch) | |
| tree | a3333a5d554f4b3e3bc265c573fc450ea6a6c466 /doc | |
| parent | 5f2a42ba359f94be29aefa0d96db530a27a269d5 (diff) | |
| download | ffmpeg-5062c60c184030e3a8d87046ff7442647cbceaee.tar.gz | |
Elaborate on the Visual C-- situation.
Originally committed as revision 4716 to svn://svn.ffmpeg.org/ffmpeg/trunk
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/faq.texi | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/faq.texi b/doc/faq.texi index e0a243154c..9497903b5c 100644 --- a/doc/faq.texi +++ b/doc/faq.texi @@ -200,10 +200,17 @@ the compilation failure then you are probably not qualified for this. @section Visual C++ produces many errors. -You need a C compiler (Visual C++ is not compliant to the C standard). +Visual C++ is not compliant to the C standard and does not support +the inline assembly used in FFmpeg. 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. For more information, see the @emph{Visual C++ compatibility} section in the FFmpeg documentation. +There have been efforts to make FFmpeg compatible with Visual C++ in the +past. However, they have all been rejected as too intrusive, especially +since MinGW does the job perfectly adequately. None of the core developers +work with Visual C++ and thus this item is low priority. Should you find +the silver bullet that solves this problem, feel free to shoot it at us. + @bye |