Sitelet https://github.com/nodejs/node/issues/3451
Skip to content

When using visual studio 2015 community to build, vcbuild says that the configuration is invalid #3451

Description

@ksambhi

I know I should be using 2013, but 2015 is similar to 2013 I think.

When I run vcbuild nosign, It says that target Release|MCD is invalid.

Full output

Looking for Visual Studio 2015
Found Visual Studio 2015
ctrpp not found in WinSDK path--using pre-gen files from tools/msvs/genfiles.
creating  icu_config.gypi
{ 'target_defaults': { 'cflags': [],
                       'default_configuration': 'Release',
                       'defines': [],
                       'include_dirs': [],
                       'libraries': []},
  'variables': { 'asan': 0,
                 'host_arch': 'x64',
                 'icu_small': 'false',
                 'node_byteorder': 'little',
                 'node_install_npm': 'true',
                 'node_prefix': '/usr/local',
                 'node_release_urlbase': '',
                 'node_shared_http_parser': 'false',
                 'node_shared_libuv': 'false',
                 'node_shared_openssl': 'false',
                 'node_shared_zlib': 'false',
                 'node_tag': '',
                 'node_use_dtrace': 'false',
                 'node_use_etw': 'true',
                 'node_use_lttng': 'false',
                 'node_use_openssl': 'true',
                 'node_use_perfctr': 'true',
                 'openssl_fips': '',
                 'openssl_no_asm': 0,
                 'python': 'C:\\Python27\\python.exe',
                 'target_arch': 'ia32',
                 'v8_enable_gdbjit': 0,
                 'v8_enable_i18n_support': 0,
                 'v8_no_strict_aliasing': 1,
                 'v8_optimized_debug': 0,
                 'v8_random_seed': 0,
                 'v8_use_snapshot': 1,
                 'want_separate_host_toolset': 1}}
creating  config.gypi
creating  config.mk
Project files generated.
C:\Users\Kishan Sambhi\Documents\Projects\node\node.sln.metaproj : error MSB4126: 
The specified solution configuration "Release|MCD" is invalid.
 Please specify a valid solution configuration using the Configuration and Platform properties 
(e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU")
 or leave those properties blank to use the default solution configuration. [C:\Use
rs\Kishan Sambhi\Documents\Projects\node\node.sln]

C:\Users\Kishan Sambhi\Documents\Projects\node>

msbuild returns a similar output to the error.

I am using visual studio 2015.
System specs:

  • 8GB of RAM
  • Intel i5 quad-core processor
  • HP Pavilion e078sa
  • Windows 8.1

Activity

  1. added
    windowsIssues and PRs related to the Windows platform.
    buildIssues and PRs related to Node.js builds or CI infrastructure.
    on Oct 20, 2015
  2. ksambhi commented on Oct 20, 2015

    @ksambhi
    Author

    Should I just use Linux or vagrant vm or docker container for now

  3. ksambhi commented on Oct 20, 2015

    @ksambhi
    Author

    I am guessing yes

  4. tflanagan commented on Oct 20, 2015

    @tflanagan
    Contributor

    Off-topic: For the sake of people with subscription notifications, please use the "Edit Comment" feature GitHub provides. (Top right of the comment box)

    People scan new issues applying the appropriate labels so people who are more attuned to help you can easily find you. Just because a label was applied, does not mean it has been solved.

  5. mathiask88 commented on Oct 21, 2015

    @mathiask88
    Contributor

    @Gum-Joe May I ask you if you have a "Platform" environment variable. You can check this at Control Panel->Advanced System Settings->Environment Variables. If yes one solution is to delete it, but I don't know which program sets this, so maybe the vcbuild.bat can be more explicit?

  6. ksambhi commented on Oct 22, 2015

    @ksambhi
    Author

    Hi,
    Thanks for your help @mathiask88
    Turn out the environment variable $Platform was set.
    After removing it, nodejs would build.
    I will now close this issue since it has been resolved

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

    buildIssues and PRs related to Node.js builds or CI infrastructure.windowsIssues and PRs related to the Windows platform.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions