updated VS studio readme

diff --git a/README.md b/README.md
index 6478964eac517b2e9974fd4ee5865717e8353cdd..58c9ab02ce9bdc9d0c2245575dcb57ff220c1e78 100644 (file)
--- a/README.md
+++ b/README.md
@@ -130,7 +130,7 @@ A Meson project is provided within `contrib/meson`.
 Going into `build` directory, you will find additional possibilities:
 - Projects for Visual Studio 2005, 2008 and 2010.
   + VS2010 project is compatible with VS2012, VS2013, VS2015 and VS2017.
-- Automated build scripts for Visual compiler by [@KrzysFR](https://github.com/KrzysFR) and [@HaydnTrigg](https://github.com/HaydnTrigg) , in `build/VS_scripts`,
+- Automated build scripts for Visual compiler by [@KrzysFR](https://github.com/KrzysFR), in `build/VS_scripts`,
   which will build `zstd` cli and `libzstd` library without any need to open Visual Studio solution.
 
 

diff --git a/build/VS_scripts/README.md b/build/VS_scripts/README.md
index 3942e381176c93d3744627104b57da6b022ae652..6ccaca7882f71882e6460dc489a5dfffb1d28708 100644 (file)
--- a/build/VS_scripts/README.md
+++ b/build/VS_scripts/README.md
@@ -7,48 +7,58 @@ Here are a few command lines for reference :
 
 Running the following command will build both the `Release Win32` and `Release x64` versions:
 ```batch
-build\build.VS2013.cmd
+build.VS2013.cmd
 ```
-The result of each build will be in the corresponding `build\bin\Release\{ARCH}\` folder.
+The result of each build will be in the corresponding `bin\Release\{ARCH}\` folder.
 
 If you want to only need one architecture:
-- Win32: `build\build.generic.cmd VS2013 Win32 Release v120`
-- x64: `build\build.generic.cmd VS2013 x64 Release v120`
+- Win32: `build.generic.cmd VS2013 Win32 Release v120`
+- x64: `build.generic.cmd VS2013 x64 Release v120`
 
 If you want a Debug build:
-- Win32: `build\build.generic.cmd VS2013 Win32 Debug v120`
-- x64: `build\build.generic.cmd VS2013 x64 Debug v120`
+- Win32: `build.generic.cmd VS2013 Win32 Debug v120`
+- x64: `build.generic.cmd VS2013 x64 Debug v120`
 
 ### Build with Visual Studio 2015 for msvcr140.dll
 
 Running the following command will build both the `Release Win32` and `Release x64` versions:
 ```batch
-build\build.VS2015.cmd
+build.VS2015.cmd
 ```
-The result of each build will be in the corresponding `build\bin\Release\{ARCH}\` folder.
+The result of each build will be in the corresponding `bin\Release\{ARCH}\` folder.
 
 If you want to only need one architecture:
-- Win32: `build\build.generic.cmd VS2015 Win32 Release v140`
-- x64: `build\build.generic.cmd VS2015 x64 Release v140`
+- Win32: `build.generic.cmd VS2015 Win32 Release v140`
+- x64: `build.generic.cmd VS2015 x64 Release v140`
 
 If you want a Debug build:
-- Win32: `build\build.generic.cmd VS2015 Win32 Debug v140`
-- x64: `build\build.generic.cmd VS2015 x64 Debug v140`
+- Win32: `build.generic.cmd VS2015 Win32 Debug v140`
+- x64: `build.generic.cmd VS2015 x64 Debug v140`
 
 ### Build with Visual Studio 2015 for msvcr120.dll
 
-You need to invoke `build\build.generic.cmd` with the proper arguments:
+This capability is offered through `build.generic.cmd` using proper arguments:
 
 **For Win32**
 ```batch
-build\build.generic.cmd VS2015 Win32 Release v120
+build.generic.cmd VS2015 Win32 Release v120
 ```
-The result of the build will be in the `build\bin\Release\Win32\` folder.
+The result of the build will be in the `bin\Release\Win32\` folder.
 
 **For x64**
 ```batch
-build\build.generic.cmd VS2015 x64 Release v120
+build.generic.cmd VS2015 x64 Release v120
 ```
-The result of the build will be in the `build\bin\Release\x64\` folder.
+The result of the build will be in the `bin\Release\x64\` folder.
 
 If you want Debug builds, replace `Release` with `Debug`.
+
+### Build with Visual Studio 2017
+
+`build.VS2017.cmd`, contributed by [@HaydnTrigg](https://github.com/HaydnTrigg),
+will build both the `Release Win32` and `Release x64` versions
+of the first VS2017 variant it finds, in this priority order :
+Enterprise > Professional > Community
+
+Alternatively, it's possible to target a specific version,
+using appropriate script, such as `build.VS2017Enterprise.cmd` for example.