On Thu, Sep 27, 2012 at 10:52:33PM -0400, Derek Buitenhuis wrote:
> --- a/doc/platform.texi
> +++ b/doc/platform.texi
> @@ -104,21 +104,75 @@ you can build all libraries as DLLs.
>
> +You will need the following prerequisites:
>
> -@subsection Using shared libraries
> +@itemize
> +@item @uref{https://github.com/rbultje/c99-to-c89/, C99-to-C89 Converter &
> Wrapper}
> +@item @uref{http://code.google.com/p/msinttypes/, msinttypes}
> +@item @uref{http://www.mingw.org/, MSYS}
> +@item @uref{http://yasm.tortall.net/, YASM}
> +@item @uref{http://gnuwin32.sourceforge.net/packages/bc.htm, bc for Windows}
> if you want to
> +run @uref{fate.html, FATE}.
> +@end itemize
Wasn't there some version of MSVC that finally provided inttypes?
> +To set up a proper MSVC environment in MSYS, you simply need to run
> @code{msys.bat}
> +from the Visual Studio command prompt.
> +
> +Caveat: Run @code{which link} to see which link you are using. If it is
> located at
> +@code{/bin/link.exe}, then you have the wrong link in your @code{PATH}.
> Either
> +move/remove that copy, or make sure MSVC's link.exe is higher up in your
> @code{PATH}
> +than coreutils'.
Mind your line length please, not just here.
> +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
> +these directories. Alternatively, you can try and use
> +@code{--extra-cflags}/@code{--extra-ldflags}.
Mention that these are flags for configure.
> +@enumerate
> +@item Grab the @uref{http://zlib.net/, zlib sources}.
> +@item Edit @code{win32/Makefile.msc} so that it uses -MT instead of -MD,
> since this
> +is how Libav is built as ell.
as _w_ell
Diego
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
