diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/faq.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/faq.texi b/doc/faq.texi index 8ace580f4f..fcb58feea1 100644 --- a/doc/faq.texi +++ b/doc/faq.texi @@ -360,10 +360,10 @@ It depends. If your compiler is C99-compliant, then patches to support it are likely to be welcome if they do not pollute the source code with @code{#ifdef}s related to the compiler. -@section Microsoft Visual C++ produces many errors. +@section Is Microsoft Visual C++ supported? -Microsoft Visual C++ is not compliant to the C standard and does not support -the inline assembly used in FFmpeg. +No. Microsoft Visual C++ is not compliant to the C99 standard and does +not - among other things - support the inline assembly used in FFmpeg. If you wish - for whatever weird reason - to use MSVC++ for your project then you can link the MSVC++ code with libav* as long as you compile the latter with a working C compiler. For more information, see @@ -372,7 +372,7 @@ documentation. There have been efforts to make FFmpeg compatible with MSVC++ 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 +since MinGW does the job adequately. None of the core developers work with MSVC++ and thus this item is low priority. Should you find the silver bullet that solves this problem, feel free to shoot it at us. |