1Command line scripts for Visual Studio compilation without IDE 2============================================================== 3 4Here are a few command lines for reference : 5 6### Build with Visual Studio 2013 for msvcr120.dll 7 8Running the following command will build both the `Release Win32` and `Release x64` versions: 9```batch 10build.VS2013.cmd 11``` 12The result of each build will be in the corresponding `bin\Release\{ARCH}\` folder. 13 14If you want to only need one architecture: 15- Win32: `build.generic.cmd VS2013 Win32 Release v120` 16- x64: `build.generic.cmd VS2013 x64 Release v120` 17 18If you want a Debug build: 19- Win32: `build.generic.cmd VS2013 Win32 Debug v120` 20- x64: `build.generic.cmd VS2013 x64 Debug v120` 21 22### Build with Visual Studio 2015 for msvcr140.dll 23 24Running the following command will build both the `Release Win32` and `Release x64` versions: 25```batch 26build.VS2015.cmd 27``` 28The result of each build will be in the corresponding `bin\Release\{ARCH}\` folder. 29 30If you want to only need one architecture: 31- Win32: `build.generic.cmd VS2015 Win32 Release v140` 32- x64: `build.generic.cmd VS2015 x64 Release v140` 33 34If you want a Debug build: 35- Win32: `build.generic.cmd VS2015 Win32 Debug v140` 36- x64: `build.generic.cmd VS2015 x64 Debug v140` 37 38### Build with Visual Studio 2015 for msvcr120.dll 39 40This capability is offered through `build.generic.cmd` using proper arguments: 41 42**For Win32** 43```batch 44build.generic.cmd VS2015 Win32 Release v120 45``` 46The result of the build will be in the `bin\Release\Win32\` folder. 47 48**For x64** 49```batch 50build.generic.cmd VS2015 x64 Release v120 51``` 52The result of the build will be in the `bin\Release\x64\` folder. 53 54If you want Debug builds, replace `Release` with `Debug`. 55 56### Build with Visual Studio 2017 57 58`build.VS2017.cmd`, contributed by [@HaydnTrigg](https://github.com/HaydnTrigg), 59will build both the `Release Win32` and `Release x64` versions 60of the first VS2017 variant it finds, in this priority order : 61Enterprise > Professional > Community 62 63Alternatively, it's possible to target a specific version, 64using appropriate script, such as `build.VS2017Enterprise.cmd` for example. 65