Conversation
|
I can reproduce the test failure on Windows. |
|
@targos can you please rebase this? If not, I'd be happy to. |
|
I checked with my computer and it seems that part of the code is really broken on recent versions of Visual Studio. The registry values that are checked do not exist on my machine. |
|
I am not a Windows user so it is difficult for me to fix this so please try to make progress on it. Given the simple mods, please feel free to create another PR and close this one if that is easier. |
|
@targos could you please look into this issue? Would it take a non-trivial amount of effort to fix? It seems like the upstream PR at nodejs/node#32698 is blocked on this. |
|
I have looked into this and it requires work that I can't do myself. This is not related to the error we saw in your PR |
|
@targos it's not related but I think we require CI on Windows in order to fix that issue. |
|
nodejs/node-gyp#1762 (comment) suggested gyp can use
|
|
Is there a common location for |
|
OK, found it: https://github.com/microsoft/vswhere
|
|
I suppose we need to run something like this: |
|
Something we could do is bundle the executable with gyp-next. It is one of the recommended ways (vswhere is MIT-licensed). /cc @joaocgreis what's the oldest version of Visual Studio that we need to support in node-gyp? |
Sounds like a pretty decent idea to me. |
No description provided.