On Thu, 27 Sep 2012, Derek Buitenhuis wrote:
Signed-off-by: Derek Buitenhuis <[email protected]> --- doc/faq.texi | 27 ++------------------------- 1 file changed, 2 insertions(+), 25 deletions(-)diff --git a/doc/faq.texi b/doc/faq.texi index 7c5373c..410562d 100644 --- a/doc/faq.texi +++ b/doc/faq.texi @@ -302,31 +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. - -@section Can you add automake, libtool or autoconf support? - -No. These tools are too bloated and they complicate the build.
I guess this last section was removed accidentally, since I don't see why it should be dropped.
// Martin _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
