Martin Storsjö

> I would like to build msvc-wine VS2017 (--major 15) with specific MSVC toolchain version (--msvc-version 15.9). But vsdownload.py shows me not find the exact version packages for 15.9 For...

This is a known issue (but which I probably haven't written down anywhere here); anything relating to PDB files doesn't really work (at least not the normal way that it's...

Yes, avoiding concurrent writes to the PDB file kind of works. For newer MSVC versions it seems like it works if you use `/Z7` instead of `/Zi` as well, for...

Oh, thanks for letting me know!

I'm somewhat ambivalent about this PR. (I haven't studied your suggested code in detail yet.) Yes, python is probably to prefer over perl for the `fixinclude` and `lowercase` scripts. But...

My main guess here, is that the paths that you pass are in a unix-y form where `cl.exe` in wine won't resolve it correctly. We do rewrite some paths in...

> As far I can see if I use --major 17 it downloads v142. I checked with MSVC_TOOLSET_VERSION in cmake According to https://cmake.org/cmake/help/latest/variable/MSVC_TOOLSET_VERSION.html, v142 is MSVC 2019 while v143 is...

> Results in the following error: > > ``` > Microsoft (R) C/C++ Optimizing Compiler Version 19.36.32535 for x64 > Copyright (C) Microsoft Corporation. All rights reserved. > > cl...

I'd suggest the following: ``` make distclean autoreconf ./configure ```

Can you do `git clean -xfd` to remove any generated file from the repo, and start over?