Changes between Version 3 and Version 4 of CompilationGuide/MSVC


Ignore:
Timestamp:
Jul 8, 2015, 6:23:25 PM (11 years ago)
Author:
hahaha1234
Comment:

format text, highlight potential issues

Legend:

Unmodified
Added
Removed
Modified

  • CompilationGuide/MSVC

    v3 v4  
    2626Finally, create an INCLUDE environment variable, and point it to c:\99, this is the location where the compiler will find inttypes.h
    2727
    28 If it complains of "MSVCR100.dll not found" when running yasm, install the microsoft 2010 VC [http://www.faqforge.com/windows/fix-the-program-cant-start-because-msvcr100-dll-is-missing-from-your-computer-error-on-windows/ redistributable]
     28''If it complains of "MSVCR100.dll not found" when running yasm, install the microsoft 2010 VC [http://www.faqforge.com/windows/fix-the-program-cant-start-because-msvcr100-dll-is-missing-from-your-computer-error-on-windows/ redistributable]
     29''
    2930
    3031To set up a proper environment in MSYS, you need to run msys.bat from the Visual Studio or Intel Compiler command prompt.
    … …  
    4445--enable-shared will generate the dynamic linked lib (dlls)
    4546
    46 you might see an error saying cl can't generate executable, this is because you installed the link.exe from msys. it conflicts with the link.exe of visual studio.
    47 you can try "which link.exe" to verify if it is the case. if you see /bin/link.exe, then you can simply rm /bin/link.exe
     47''you might see an error saying cl can't generate executable, this is because you installed the link.exe from msys. it conflicts with the link.exe of visual studio.
     48''
     49you can try "which link.exe" to verify if it is the case. if you see /bin/link.exe, then you can simply rm /bin/link.exe See here for details: [https://trac.ffmpeg.org/ticket/3203]
     50
    4851the right link.exe should come from this location:
     52
    4953/c/Program Files (x86)/Microsoft Visual Studio 12.0/VC/BIN/link.exe
    5054
    5155you might see two problems when building ffmpeg:
    52 1. pr command not found:
     56''1. pr command not found:
     57''
     58
    5359please take a look at here [http://creekcodes.blogspot.com/2011/02/msys-pr-not-found.html]
    5460basically pr.exe is removed from msys, you need to download it from here [http://sourceforge.net/projects/mingw/files/MSYS/Base/msys-core/_obsolete/coreutils-5.97-MSYS-1.0.11-2/coreutils-5.97-MSYS-1.0.11-snapshot.tar.bz2/download] and copy pr.exe to the msys/bin folder.
    5561
    56 2. the compiler might complain about redefinition issues of stdint.h, because both msinttypes and visual studio have stdint.h. I removed stdint.h from c:\c99 to let the compiler uses the one provided by visual studio.
     62''2. the compiler might complain about redefinition issues of stdint.h, because both msinttypes and visual studio have stdint.h. I removed stdint.h from c:\c99 to let the compiler uses the one provided by visual studio.
     63''
    5764
    5865in the end of configuration, you might also see pkg-config not found issue. that won't affect compilation, you can ignore it. it is said that installing pkg-config to msys is kinda tiresome.
    … …  
    6067
    6168How to build debug version?
     69
    6270an example:
     71
    6372$ ./configure --enable-asm --enable-yasm --disable-ffserver --disable-avdevice --disable-doc --disable-ffplay --disable-ffprobe --disable-ffmpeg --enable-shared --disable-static --disable-bzlib --disable-libopenjpeg --disable-iconv --disable-zlib --prefix=/c/ffmpeg --toolchain=msvc --arch=amd64 --extra-cflags="-MDd" --extra-ldflags="/NODEFAULTLIB:libcmt" --enable-debug