diff options
| author | Ramiro Polla <ramiro.polla@gmail.com> | 2007-11-10 13:23:22 +0000 |
|---|---|---|
| committer | Ramiro Polla <ramiro.polla@gmail.com> | 2007-11-10 13:23:22 +0000 |
| commit | 19671d3faf9487baaf5df83a303356235e9388fc (patch) | |
| tree | c314300244dc2dd92c9eb68830c2c213c14d2258 /doc/faq.texi | |
| parent | ba6d9eb3f602e7361b2e8c493d1e9baeceb39680 (diff) | |
| download | ffmpeg-19671d3faf9487baaf5df83a303356235e9388fc.tar.gz | |
Express opinion in a less aggressive manner.
Originally committed as revision 10995 to svn://svn.ffmpeg.org/ffmpeg/trunk
Diffstat (limited to 'doc/faq.texi')
| -rw-r--r-- | doc/faq.texi | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/faq.texi b/doc/faq.texi index fcb58feea1..5fffd8c81e 100644 --- a/doc/faq.texi +++ b/doc/faq.texi @@ -364,7 +364,7 @@ with @code{#ifdef}s related to the compiler. 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 +If you wish 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 the @emph{Microsoft Visual C++ compatibility} section in the FFmpeg @@ -376,6 +376,8 @@ 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. +We strongly recommend you to move over from MSVC++ to MinGW tools. + @section Can I use FFmpeg or libavcodec under Windows? Yes, but the Cygwin or MinGW tools @emph{must} be used to compile FFmpeg. |