README-windows.txt 1.6 KB

12345678910111213141516171819202122232425262728293031323334353637
  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. There is a script (check.bin.compatibility.vs2010.bat) in VisualC\build-scripts
  6. which will build <sdl_root>\VisualC (which is not generated by this premake
  7. system) and build SDL2.dll using the generated SDL2.sln in the VS2010 folder. It
  8. will copy the SDL2.dll over to each test project in <sdl_root>\VisualC and
  9. subsequently run those tests to verify binary compatibility between the SDL2.dll
  10. that came from the premake solution and the executables which were built using
  11. the old solution files.
  12. The windows project currently depends on most of the libraries inherently
  13. added to the links list by Visual Studio. The additional libraries SDL2 depends
  14. on are as follows:
  15. -imm32
  16. -oleaut32
  17. -winmm
  18. -version
  19. -OpenGL32
  20. -DirectX
  21. OpenGL32 is an optional dependency. If it is not located for whatever reason,
  22. SDL2 will build fine without it. DirectX is another optional dependency for
  23. SDL2. Unlike the manually-created VS projects, the meta-build system supports
  24. not having DirectX support and still being able to build and run through most of
  25. the projects (using the OpenGL renderer or the software renderer).
  26. Run the clean script to clear out the directory of VS-related files and
  27. binaries.
  28. Ben:
  29. Please note that the script for building the VS2012 solution from the
  30. command prompt seems to not be working properly. This issue is
  31. currently unresolved.