| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2018-10-16 | format code | ruki | |
| 2018-10-15 | fix find_vstudio when executing from an already defined MSVC command prompt | Roy Ivy III | |
| .# Discussion Older MSVC/VS versions don't define the "VisualStudioVersion" environment variable. Prior to this fix, when executing within an already prepared environment (eg, the "Visual Studio Command Prompt") with those older MSVC/VS builds, the search logic would incorrectly try to search for all installed versions and read their environments. But since the environment had already been prepped, executing `vsvarsall` for any found MSVC/VS versions resulted in a superimposed and confused/invalid environment. For the older MSVC/VS versions without "VisualStudioVersion", this fix does use heuristics to guess at the correct version (and it's corresponding vsvers value [used as the results key value]). But, even if the wrong version is guessed, the results from find_vstudio are clean, without any environmental superposition, and fully usable for compilation. | |||
| 2018-10-15 | fix "fix UCRTVersion" logic for possibly missing WindowsSDKVersion | Roy Ivy III | |
| * some versions (especially early versions) of MSVC/VS may not define the WindowsSDKVersion environment variable | |||
| 2018-10-15 | improve find_rc | ruki | |
| 2018-10-15 | improve find_vswhere and find_vstudio | ruki | |
| 2018-10-14 | fix detection strategy for MSVC/VS2017+ | Roy Ivy III | |
| * fixes the MSVC/VS 2017 detection problem discussed within <https://github.com/tboox/xmake/issues/225> .# Discussion MSVC/VS versions >= 15.0 will no longer be setting registry entries for tool location purposes. But `vswhere` (included with MSVC/VS versions >= 15.2, and placed in a guaranteed location) can instead be used to find the needed path. `os.runv(...)` is used as the tool to gather `vswhere` output instead of `($shell ...)` in order to avoid some `($shell ...)` limitations. Commands containing white space and/or special characters (eg, '[', ')') are difficult or impossible to pass through the current `($shell ...)` implementation, causing application exceptions. Both white space and the noted special characters are needed to construct the required `vswhere` command. ref: <https://github.com/Microsoft/vswhere/blob/master/README.md> @@ <https://archive.is/mEmdu> | |||
| 2018-10-14 | fix missing rc.exe and add find_vswhere | ruki | |
| 2018-09-04 | Fix bug for VS2003 can't be found | 夕伽 | |
| (xmake config --vs=2003) | |||
| 2018-08-17 | improve find_vstudio | ruki | |
| 2018-06-27 | fix find_vstudio bug | ruki | |
| 2018-05-22 | improve find_vstudio | ruki | |
| 2018-04-28 | fix ucrt version for find_vstudio | ruki | |
| 2018-03-27 | add vsvaralls bat path | ruki | |
| 2017-12-28 | update copyright date | ruki | |
| 2017-11-29 | fix generate vcvarsall data file error | ruki | |
| 2017-08-27 | update description and index | ruki | |
| 2017-06-30 | get vstudio sdk version | ruki | |
| 2017-06-19 | impl has_flags and rename detect.xxx to detect.xxxs | ruki | |
