Skip to content

Releases: metastack/msvs-tools

MSVS Tools 0.8.0

20 Nov 22:08

Choose a tag to compare

MSVS Tools 0.7.0

08 Mar 17:27

Choose a tag to compare

  • Various shellcheck overhauls and other hardening (#16, @dra27)
  • Preview versions of Visual Studio are now included in results (#17, @dra27)
  • New options --installed and --output=data (#17, @dra27)
  • Various fixes to environment compiler detection and results (#17, @dra27)
  • opam packaging for msvs-detect exposed as conf-msvc32 and conf-msvc64 packages (#18, @dra27)

MSVS Tools 0.6.0

21 Nov 15:26

Choose a tag to compare

  • Add metadata for Visual Studio 2022 (#13, @dra27)
  • Simplify the search of the Microsoft Linker in msvs-promote-path (#14, @shym)

MSVS Tools 0.5.0

06 Sep 09:17

Choose a tag to compare

  • Use MSYS2_ARG_CONV_EXCL to disable MSYS2 argument mangling, replacing the workaround in 0.4.0 (#8, @jonahbeckford)
  • Handle special characters in PATH in msvs-promote-path. In particular, stray double-quote characters don't corrupt the command line. (#10)
  • Fix strong/weak detection of the environment compiler (#9, @jonahbeckford)
  • Fix the vswhere invocation to detect Build Tools (#9, @jonahbeckford)

MSVS Tools 0.4.1

26 Jun 13:20

Choose a tag to compare

  • Apply various fixes and clarifications from shellcheck (#7, @MisterDA)
  • Improve tail-stripping of MSVS_PATH to prevent path blow-out, especially when run from within a developer command prompt (or when msvs-detect is invoked recursively).
  • Ensure PATH-mangling never overrides Cygwin bin (in particular, ensure which is always from the same Cygwin as the script)

MSVS Tools 0.4.0

13 Jun 13:46

Choose a tag to compare

Bug fixes for msvs-detect:

  • Visual Studio 2019 will now be selected by default
  • The script now works inside MSYS2, which previously was treating the switches in cmd /v:on /c as MSYS2-style paths
  • The environment compiler is excluded if LIB and INCLUDE are invalid (i.e. if the user has manually added cl.exe to PATH).

MSVS Tools 0.3.2

03 Jan 13:29

Choose a tag to compare

Commands tested by msvs-promote-path can no longer leak output to stderr.

Bug fixes for msvs-detect:

  • Visual Studio 2017 detection worked, but was not useful since updates increment the version number (so Visual Studio 2017 Update 5 is 15.5 whereas Visual Studio 2015 Update 3 is still 14.0). This has been fixed by allowing wildcards in MSVS_PREFERENCE so VS15.* means to select the most recent installed update of Visual Studio 2017. It is possible to specify specific updates (e.g. VS15.5) for particularly niche uses.
  • Escaping of special characters was broken inasmuch as it was completely missing. --output=shell will now correctly escape directory names which nefariously include a single quote and --output=make will now escape both # and $ meaning that the directory names of certain programming languages containing musical symbols in their names no longer unexpectedly comment out Makefile lines.
  • Strings for --output=make were being unnecessarily assigned to variables using := and also incorrectly double-quoted.

MSVS Tools 0.3.1

03 Jan 13:21

Choose a tag to compare

One case missed for the Cygwin \r change in msvs-detect

MSVS Tools 0.3.0

03 Jan 13:21

Choose a tag to compare

msvs-detect updated to support Visual Studio 2017. Detection is done via vswhere which is automatically installed for Update 2 and later. Detection of the original release and Update 1 requires vswhere.exe to be downloaded and placed with the script.

msvs-detect works correctly with newer Cygwin tools which no longer strip \r from the output of native executables.

MSVS Tools 0.2.0

03 Jan 13:16

Choose a tag to compare

MSVS_NAME is now included in the output of msvs-detect which describes the software package providing the compiler selected.