On 28/09/2012 3:28 AM, Diego Biurrun wrote:
>> +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.
Fixed.
>> +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.
Done.
>> +@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
Fixed.
- Derek
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
