User Tools

Site Tools


development:compiling:player:windows:visual-studio

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
development:compiling:player:windows:visual-studio [2013/02/24 00:03] – new compile instructions ghabrydevelopment:compiling:player:windows:visual-studio [2016/04/01 17:35] – remove boost fdelapena
Line 17: Line 17:
 To compile open a Visual Studio Command Prompt (32 or 64 bit) and execute ''build_vs2010.cmd'' (the Command Prompt can be found in the start menu). To compile open a Visual Studio Command Prompt (32 or 64 bit) and execute ''build_vs2010.cmd'' (the Command Prompt can be found in the start menu).
  
-=== Compiling with Visual Studio 2012 ===+== Compiling with Visual Studio 2012 ==
 ''If you compiled using VS2010 you can skip this part.'' ''If you compiled using VS2010 you can skip this part.''
  
-To compile open a Visual Studio Command Prompt (32 or 64 bit).+To compile open a Visual Studio Command Prompt (32 or 64 bit). The Command Prompt can be found in the start menu.
  
-The precompiled libraries are only tested with VS2010. Possible workarounds:+The precompiled libraries are only tested with VS2010 and don't compile directly using VS2012. Possible workarounds:
  
   - Install Visual Studio 2010 too and follow the instructions above.   - Install Visual Studio 2010 too and follow the instructions above.
Line 32: Line 32:
 The resulting files appear in vs2010. The resulting files appear in vs2010.
  
-The boost ([[http://www.boost.org/]]) headers are not included because of their gigantic filesize. The boost folder must be placed in ''vs2010/include/boost''+You will need to manually add the EASYDEV_MSVC enviroment variable and target the path vs2010 otherwise the EasyRPG solution file can't find the libraries.
- +
-You will need to manually add the EASYDEV_MSVC enviroment variable and target the path where you place them.+
  
 To create new environment variables enter the "Windows Control Panel" and select "System" (or enter "environment variable" in the search field). Sometimes new environment variables are not detected. Logout and -in again in order to fix this. To create new environment variables enter the "Windows Control Panel" and select "System" (or enter "environment variable" in the search field). Sometimes new environment variables are not detected. Logout and -in again in order to fix this.
Line 44: Line 42:
  
   * DirectX SDK (February 2010)   * DirectX SDK (February 2010)
-  * expat 2.1.0 +  * expat 
-  * freetype 2.4.11 +  * freetype 
-  * libjpeg 9 +  * libjpeg 
-  * libmad 0.15.1b +  * libmad 
-  * libmikmod 3.2.0 +  * libmikmod 
-  * libogg 1.3.0 +  * libogg 
-  * libpng 1.5.14 +  * libpng 
-  * libvorbis 1.3.3 +  * libvorbis 
-  * libvorbisfile 1.3.3 (included with libvorbis)+  * libvorbisfile (included with libvorbis)
   * native_midi (included with SDL_mixer)   * native_midi (included with SDL_mixer)
-  * Pixman 0.28.2 +  * Pixman 
-  * SDL 1.2.15 +  * SDL2 
-  * SDL_image 1.2.12 (BMP, GIF, JPG, PNG support) +  * SDL2_mixer (WAV, MOD, MP3, OGG and MID support) 
-  * SDL_mixer 1.2.12 (WAV, MOD, MP3, OGG and MID support) +  * zlib
-  * SDL_ttf 2.0.11 +
-  * zlib 1.2.7+
  
 ===== Compiling Player ===== ===== Compiling Player =====
  
-You need to place the [[https://github.com/EasyRPG/Readers|Readers library]] sources into the player lib/readers folder.+You need to place the [[https://github.com/EasyRPG/liblcf|liblcf]] sources into the player lib/liblcf folder.
  
 Open the solution file in ''player\builds\vs2010'', select "Debug" or "Release" configuration from the configuration manager pulldown menu and then go to Build->Build solution, or just press Control-F7 to compile it. Open the solution file in ''player\builds\vs2010'', select "Debug" or "Release" configuration from the configuration manager pulldown menu and then go to Build->Build solution, or just press Control-F7 to compile it.
  
 The Player executable should be in the folder ''bin''. If you are not using the precompiled libraries, and you have dynamically linked Player, you will need to place the required .dll in the same folder Player.exe is. The Player executable should be in the folder ''bin''. If you are not using the precompiled libraries, and you have dynamically linked Player, you will need to place the required .dll in the same folder Player.exe is.
 +
 +===== Troubleshooting =====
 +
 +==== "Already defined" linker error ====
 +
 +This usually happens if you link against the wrong visual studio runtime and shouldn't happen if you follow the build instructions mentioned above.
 +
 +If you got the libraries from other sources make sure that their runtime library (Project Properties -> C++ -> Code generation) is set to "Multithreaded Debug" (/MTd) for debug and "Multithreaded" (/MT) for release. To hide the error go to "Project Properties -> Linker -> Input -> Ignore Specific Default Libraries" and ignore LIBCMT.LIB or LIBCMTD.LIB (ignoring one of them should remove the error but it's recommended to link the libs against the correct library instead!).
 +
 +==== LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt ====
 +
 +Press compile again, then linking should succeed, if not:
 +
 +This error happens because of conflict of two versions of cvtres.exe if you have Visual Studio 2010 and 2012 installed on same PC. To fix it, go to the bin directory of Visual Studio 2010 (usually C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\) and rename cvtres.exe to cvtres0.exe. It will not break the linker of 2010.
development/compiling/player/windows/visual-studio.txt · Last modified: 2022/12/28 16:19 by carstene1ns

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki