Signed-off-by: Derek Buitenhuis <[email protected]>
---
doc/platform.texi | 21 +++++++++++++--------
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/doc/platform.texi b/doc/platform.texi
index 80dd029..5c3dc4f 100644
--- a/doc/platform.texi
+++ b/doc/platform.texi
@@ -101,10 +101,10 @@ you can build all libraries as DLLs.
@end itemize
-@section Microsoft Visual C++
+@section Microsoft Visual C++ or Intel C++ Compiler for Windows
-Libav can be built with MSVC using a C99-to-C89 conversion utility and
-wrapper.
+Libav can be built with MSVC or ICL using a C99-to-C89 conversion utility and
+wrapper. For ICL, only the wrapper will be used, since it supports C99.
You will need the following prerequisites:
@@ -117,28 +117,33 @@ You will need the following prerequisites:
you want to run @uref{fate.html, FATE}.
@end itemize
-To set up a proper MSVC environment in MSYS, you simply need to run
-@code{msys.bat} from the Visual Studio command prompt.
+To set up a proper environment in MSYS, you simply need to run
+@code{msys.bat} from the Visual Studio or Intel Compiler command prompt.
Place @code{makedef}, @code{c99wrap.exe}, @code{c99conv.exe}, and
@code{yasm.exe}
somewhere in your @code{PATH}.
Next, make sure @code{inttypes.h} and any other headers and libs you want to
use
-are located in a spot that MSVC can see. Do so by modifying the @code{LIB} and
-@code{INCLUDE} environment variables to include the @strong{Windows} paths to
+are located in a spot that the compiler can see. Do so by modifying the
@code{LIB}
+and @code{INCLUDE} environment variables to include the @strong{Windows} paths
to
these directories. Alternatively, you can try and use the
@code{--extra-cflags}/@code{--extra-ldflags} configure options.
Finally, run:
@example
+For MSVC:
./configure --toolchain=msvc
+
+For ICL:
+./configure --toolchain=icl
+
make
make install
@end example
If you wish to compile shared libraries, add @code{--enable-shared} to your
-configure options. Note that due to the way MSVC handles DLL imports and
+configure options. Note that due to the way MSVC and ICL handle DLL imports and
exports, you cannot compile static and shared libraries at the same time, and
enabling shared libraries will automatically disable the static ones.
--
1.8.3.1
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
