premake/README-windows.txt
changeset 7925 f090a47eb7f7
equal deleted inserted replaced
7924:fcb86d323770 7925:f090a47eb7f7
       
     1 Use the Visual Studio batch files (located in the VisualC folder) to
       
     2 conveniently generate solutions for Visual Studio 2008, 2010, and 2012.
       
     3 It also contains a cleaner script and a convenient script for automatically
       
     4 running all the test suites.
       
     5 
       
     6 There is a script (check.bin.compatibility.vs2010.bat) in VisualC\build-scripts
       
     7 which will build <sdl_root>\VisualC (which is not generated by this premake
       
     8 system) and build SDL2.dll using the generated SDL2.sln in the VS2010 folder. It
       
     9 will copy the SDL2.dll over to each test project in <sdl_root>\VisualC and
       
    10 subsequently run those tests to verify binary compatibility between the SDL2.dll
       
    11 that came from the premake solution and the executables which were built using
       
    12 the old solution files.
       
    13 
       
    14 The windows project currently depends on most of the libraries inherently
       
    15 added to the links list by Visual Studio. The additional libraries SDL2 depends
       
    16 on are as follows:
       
    17 
       
    18   -imm32
       
    19   -oleaut32
       
    20   -winmm
       
    21   -version
       
    22   -OpenGL32
       
    23   -DirectX
       
    24 
       
    25 OpenGL32 is an optional dependency. If it is not located for whatever reason,
       
    26 SDL2 will build fine without it. DirectX is another optional dependency for
       
    27 SDL2. Unlike the manually-created VS projects, the meta-build system supports
       
    28 not having DirectX support and still being able to build and run through most of
       
    29 the projects (using the OpenGL renderer or the software renderer).
       
    30 
       
    31 Run the clean script to clear out the directory of VS-related files and
       
    32 binaries.
       
    33 
       
    34 Ben:
       
    35 Please note that the script for building the VS2012 solution from the
       
    36 command prompt seems to not be working properly. This issue is
       
    37 currently unresolved.