On 09/27/2012 10:02 PM, Derek Buitenhuis wrote: > Signed-off-by: Derek Buitenhuis <[email protected]> > --- > doc/faq.texi | 23 ++--------------------- > 1 file changed, 2 insertions(+), 21 deletions(-) > > diff --git a/doc/faq.texi b/doc/faq.texi > index 7c5373c..53afc88 100644 > --- a/doc/faq.texi > +++ b/doc/faq.texi > @@ -302,27 +302,8 @@ with @code{#ifdef}s related to the compiler. > > @section Is Microsoft Visual C++ supported? > > -No. Microsoft Visual C++ is not compliant to the C99 standard and does > -not - among other things - support the inline assembly used in Libav. > -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 Libav > -documentation. > - > -There have been efforts to make Libav compatible with MSVC++ in the > -past. However, they have all been rejected as too intrusive, especially > -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 Libav under Windows? > - > -Yes, but the Cygwin or MinGW tools @emph{must} be used to compile Libav. > -Read the @emph{Windows} section in the Libav documentation to find more > -information. > +Yes. Please see the @uref{platform.html#Microsoft-Visual-C_002b_002b, > Microsoft Visual C++} > +section in the Libav documentation.
Point to all the options available not just msvc, the rest look fine. lu _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
