Skip to content

Can't build with Visual Studio 2017 Express #1881

Closed
Closed
Can't build with Visual Studio 2017 Express#1881
Labels
Windows

Description

@ectudor
ectudor
opened on Sep 20, 2019
  • Node Version: v10.16.3 - 6.10.3
  • Platform: Windows 10
  • Compiler: MSBUILD 15.9.21.664 / CL 19.16.27027.1 for x64
  • Module: node-rfc
Verbose output (from npm or node-gyp): 
Paste your log here, between the backticks. It can be:
Error: gyp info it worked if it ends with ok
gyp info using node-gyp@5.0.3
gyp info using node@10.16.3 | win32 | x64
gyp info find Python using Python version 2.7.16 found at "C:\Python27\python.exe"
gyp ERR! find VS
gyp ERR! find VS msvs_version was set from command line or npm config
gyp ERR! find VS - looking for Visual Studio version 2017
gyp ERR! find VS running in VS Command Prompt, installation path is:
gyp ERR! find VS "C:\Program Files (x86)\Microsoft Visual Studio\2017\WDExpress"
gyp ERR! find VS - will only use this version
gyp ERR! find VS checking VS2017 (15.9.28307.423) found at:
gyp ERR! find VS "C:\Program Files (x86)\Microsoft Visual Studio\2017\WDExpress"
gyp ERR! find VS - found "Visual Studio C++ core features"
gyp ERR! find VS - missing any VC++ toolset
gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS looking for Visual Studio 2013
gyp ERR! find VS - not found
gyp ERR! find VS msvs_version does not match this VS Command Prompt or the
gyp ERR! find VS installation cannot be used.

It looks like it can find the standard libraries but can't find the sdk?
I'm sure I have the sdks because I also have C++ programs that use windows api.

Note: I can't use the standalone vc++ build tools as it can't be used in enterprise when I don't have enterprise/pro visual studio license.

Thanks in advance.

Activity

  1. cclauss
    added
    Windows
    on Sep 25, 2019

  2. joaocgreis commented on Oct 1, 2019

    @joaocgreis
    joaocgreis
    on Oct 1, 2019
    Member

    I can reproduce.

    Node-gyp looks for the component Microsoft.VisualStudio.Component.VC.Tools.x86.x64 because it is present when both the Toolset and the files MSBuild needs to use it are present. But the Express edition does not have this component. I'll see if a different combination of components can be used.

  3. joaocgreis
    added a commit that references this issue on Oct 2, 2019

    win: support VS 2017 Desktop Express

    c99339d
  4. rvagg
    closed this as completedin 968c906on Oct 3, 2019
  5. rvagg
    added 3 commits that reference this issue on Oct 3, 2019

    win: support VS 2017 Desktop Express

    b0fc071

    win: support VS 2017 Desktop Express

    c169250

    win: support VS 2017 Desktop Express

    735d961
  6. ecartz
    added a commit that references this issue on May 12, 2025

    win: support VS 2017 Desktop Express

    968c906
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Windows

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions