Error MSB8007: The platform for project 'validation.vcxproj' is invalid. Platform='x64' about websocket-node HOT 19 CLOSED

Unfortunately, I'm not a C/C++ developer, and definitely not a Windows
developer. I haven't really used Visual Studio in 10 years. This native
extension was provided by the community and I must graciously rely upon
others in the community to tackle these issues. Please let me know if you
make any headway on this!

On Sat, Aug 11, 2012 at 7:55 PM, Nils [email protected] wrote:

Hi there,

Npm seems to be complaining about not being able to validate the package
for x64 architecture. I've been playing around with installing/uninstalling
Visual Studio 2010 and the Windows 7 SDK. But I guess I only need Visual
Studio 2010. Not sure what's going on. I'm running Windows 7 Home Premium
64-bit with Visual Studio 2010 installed.

$ npm install websocket
npm http GET https://registry.npmjs.org/websocket
npm http 304 https://registry.npmjs.org/websocket
npm WARN package.json [email protected] No README.md file found!

[email protected] install
c:\Users\nils\workspace\node-projects\valgomat\node_modules\websocket
node-gyp rebuild

c:\Users\nils\workspace\node-projects\valgomat\node_modules\websocket>node
"c:\Program Files\nodejs
node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js"
rebuild
C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.Cpp.InvalidPlatform.Targets(23,7):
erro
r MSB8007: The Platform for project 'validation.vcxproj' is invalid.
Platform='x64'. You may be se
eing this message because you are trying to build a project without a
solution file, and have speci
fied a non-default Platform that doesn't exist for this project.
[c:\Users\nils\workspace\node-proj
ects\valgomat\node_modules\websocket\build\validation.vcxproj]
gyp ERR! build error
gyp ERR! stack Error:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe failed with
exit c
ode: 1
gyp ERR! stack at ChildProcess.onExit (c:\Program
Files\nodejs\node_modules\npm\node_modules\nod
e-gyp\lib\build.js:215:23)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:91:17)
gyp ERR! stack at Process._handle.onexit (child_process.js:674:10)
gyp ERR! System Windows_NT 6.1.7600
gyp ERR! command "node" "c:\Program
Files\nodejs\node_modules\npm\node_modules\node-gyp\bin
node-gyp.js" "rebuild"
gyp ERR! cwd
c:\Users\nils\workspace\node-projects\valgomat\node_modules\websocket
gyp ERR! node -v v0.8.6
gyp ERR! node-gyp -v v0.6.3
gyp ERR! not ok
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! cmd "/c" "node-gyp rebuild" failed with 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the websocket package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls websocket
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7600
npm ERR! command "c:\Program Files\nodejs\node.exe" "c:\Program
Files\nodejs\node_modules\npm
\bin\npm-cli.js" "install" "websocket"
npm ERR! cwd c:\Users\nils\workspace\node-projects\valgomat
npm ERR! node -v v0.8.6
npm ERR! npm -v 1.1.48
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! c:\Users\nils\workspace\node-projects\valgomat\npm-debug.log
npm ERR! not ok code 0

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/63.

Brian McKelvey
C.E.O & Co-Founder
Worlize Inc.
www.worlize.com

from websocket-node.

Thanks for the prompt response. I don't have a lot of experience with MS-dev stuff either. Just trying to get grunt-reload to work, which relies on websocket, which relies on node-gyp. ^^ The github page for node-gyp seems to have some issues related to this:

• Build problems on Win7 x64
• There was this commit 14 days ago, that might've solved the problem. Make linking 64-bit addons with VCExpress 2010 + Windows 7.1 SDK work out of the box. Does this change to node-gyp automatically end up in websocket?

Hmm. Guess this is the best I can do about researching this issue for now. :)

from websocket-node.

Awesome, thank you for the links! I'll check it out.

Brian

On Sun, Aug 12, 2012 at 5:26 AM, Nils [email protected] wrote:

Thanks for the prompt response. I don't have a lot of experience with
MS-dev stuff either. Just trying to get grunt-reload to work, which relies
on websocket, which relies on node-gyp. ^^ The github page for node-gyp
seems to have some issues related to this:

• Build problems on Win7 x64nodejs/node-gyp#113
• There was this commit 14 days ago, that might've solved the problem. Make
  linking 64-bit addons with VCExpress 2010 + Windows 7.1 SDK work out of the
  box nodejs/node-gyp#113. Does this
  change to node-gyp automatically end up in websocket?

Hmm. Guess this is the best I can do about researching this issue for now.
:)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/63#issuecomment-7675168.

Brian McKelvey
C.E.O & Co-Founder
Worlize Inc.
www.worlize.com

from websocket-node.

node-gyp is supposed to be distributed as part of the base node.js package.
It should get updated when node gets updated. You can also try:

C:>npm install node-gyp

Brian

On Sun, Aug 12, 2012 at 5:26 AM, Nils [email protected] wrote:

Thanks for the prompt response. I don't have a lot of experience with
MS-dev stuff either. Just trying to get grunt-reload to work, which relies
on websocket, which relies on node-gyp. ^^ The github page for node-gyp
seems to have some issues related to this:

• Build problems on Win7 x64nodejs/node-gyp#113
• There was this commit 14 days ago, that might've solved the problem. Make
  linking 64-bit addons with VCExpress 2010 + Windows 7.1 SDK work out of the
  box nodejs/node-gyp#113. Does this
  change to node-gyp automatically end up in websocket?

Hmm. Guess this is the best I can do about researching this issue for now.
:)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/63#issuecomment-7675168.

Brian McKelvey
C.E.O & Co-Founder
Worlize Inc.
www.worlize.com

from websocket-node.

I "think" I've progressed somewhat. Stopped getting errors after starting to use the win7.1 sdk command prompt. Now it just hangs at node-gyp rebuild, node-gyp configure specifically. The verbose output didn't tell me much so I opened an issue at node-gyp about this.

from websocket-node.

I'm in the process of checking in some changes to the way the build process
works. I'll be releasing version 1.0.7 in the next 30 mins. Try that
version and let me know what happens. It seems to build just fine for me
on Windows 7 x64 under both Node v0.6.18 and v0.8.6. I'm not using any
particular special command prompt, just the normal one. (I don't know
anything about a win7.1 sdk)

Brian

On Sun, Aug 12, 2012 at 2:40 PM, Nils [email protected] wrote:

I "think" I've progressed somewhat. Stopped getting errors after starting
to use the win7.1 sdk command prompt. Now it just hangs at node-gyp
rebuild, node-gyp configure specifically. The verbose output didn't tell me
much so I opened an issuehttps://github.com/TooTallNate/node-gyp/issues/121at node-gyp about this.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/63#issuecomment-7680151.

Brian McKelvey
C.E.O & Co-Founder
Worlize Inc.
www.worlize.com

from websocket-node.

I just noticed in the issue you opened on node-gyp that you said you were
running git bash. I haven't tried building for windows under git-bash,
only in the normal windows command prompt.

Brian

On Sun, Aug 12, 2012 at 4:11 PM, Brian McKelvey [email protected] wrote:

I'm in the process of checking in some changes to the way the build
process works. I'll be releasing version 1.0.7 in the next 30 mins. Try
that version and let me know what happens. It seems to build just fine for
me on Windows 7 x64 under both Node v0.6.18 and v0.8.6. I'm not using any
particular special command prompt, just the normal one. (I don't know
anything about a win7.1 sdk)

Brian

On Sun, Aug 12, 2012 at 2:40 PM, Nils [email protected] wrote:

I "think" I've progressed somewhat. Stopped getting errors after starting
to use the win7.1 sdk command prompt. Now it just hangs at node-gyp
rebuild, node-gyp configure specifically. The verbose output didn't tell me
much so I opened an issuehttps://github.com/TooTallNate/node-gyp/issues/121at node-gyp about this.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/63#issuecomment-7680151.

Brian McKelvey
C.E.O & Co-Founder
Worlize Inc.
www.worlize.com

Brian McKelvey
C.E.O & Co-Founder
Worlize Inc.
www.worlize.com

from websocket-node.

Ok I just published v1.0.7! Try that out and let me know how it goes.

from websocket-node.

Here's a screenshot of my success installing the module on Windows 7:

from websocket-node.

Thank you for your effort. :) I fear I'm missing some component even though I have both Visual Studio 2010 and Win7.1 sdk installed. Running this in the Win7 sdk command prompt works to a point, but it stops at node install.js. Hmm. I'm going to try and reinstall some stuff. I may have messed up my environmental variables.

C:\test>npm install websocket --verbose
npm info it worked if it ends with ok
npm verb cli [ 'C:\Program Files\nodejs\node.exe',
npm verb cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
npm verb cli 'install',
npm verb cli 'websocket',
npm verb cli '--verbose' ]
npm info using [email protected]
npm info using [email protected]
npm verb node symlink C:\Program Files\nodejs\node.exe
npm verb config file C:\Users\nils.npmrc
npm verb config file C:\Program Files\nodejs\etc\npmrc
npm verb config file C:\Program Files\nodejs\node_modules\npm\npmrc
npm verb read json C:\test\package.json
npm verb read json C:\test\node_modules\websocket\package.json
npm verb read json C:\test\package.json
npm verb cache add [ 'websocket', null ]
npm verb parsed url { pathname: 'websocket', path: 'websocket', href: 'websocket
' }
npm verb lock websocket C:\Users\nils\AppData\Roaming\npm-cache\67c371fd-websock
et.lock
npm verb addNamed [ 'websocket', '' ]
npm verb addNamed [ null, '' ]
npm verb lock websocket@ C:\Users\nils\AppData\Roaming\npm-cache\75462c75-websoc
ket.lock
npm verb url raw websocket
npm verb url resolving [ 'https://registry.npmjs.org/', './websocket' ]
npm verb url resolved https://registry.npmjs.org/websocket
npm info retry registry request attempt 1 at 13:53:18
npm verb etag "1QDMMSUFG1Z4YMP2EWTRR27N0"
npm http GET https://registry.npmjs.org/websocket
npm http 304 https://registry.npmjs.org/websocket
npm verb etag websocket from cache
npm verb addNamed [ 'websocket', '1.0.7' ]
npm verb addNamed [ '1.0.7', '1.0.7' ]
npm verb lock [email protected] C:\Users\nils\AppData\Roaming\npm-cache\d81c032f-w
ebsocket-1-0-7.lock
npm verb read json C:\Users\nils\AppData\Roaming\npm-cache\websocket\1.0.7\packa
ge\package.json
npm info install [email protected] into C:\test
npm info installOne [email protected]
npm verb from cache C:\Users\nils\AppData\Roaming\npm-cache\websocket\1.0.7\pack
age\package.json
npm info C:\test\node_modules\websocket unbuild
npm verb from cache C:\test\node_modules\websocket\package.json
npm info preuninstall [email protected]
npm info uninstall [email protected]
npm verb true,C:\test\node_modules,C:\test\node_modules unbuild [email protected]
npm info postuninstall [email protected]
npm verb tar unpack C:\Users\nils\AppData\Roaming\npm-cache\websocket\1.0.7\pack
age.tgz
npm verb lock C:\test\node_modules\websocket C:\Users\nils\AppData\Roaming\npm-c
ache\d56ef91e-C-test-node-modules-websocket.lock
npm verb read json C:\test\node_modules\websocket\package.json
npm info preinstall [email protected]
npm verb from cache C:\test\node_modules\websocket\package.json
npm verb readDependencies using package.json deps
npm verb from cache C:\test\node_modules\websocket\package.json
npm verb readDependencies using package.json deps
npm verb about to build C:\test\node_modules\websocket
npm info build C:\test\node_modules\websocket
npm verb from cache C:\test\node_modules\websocket\package.json
npm verb linkStuff [ false, false, false, 'C:\test\node_modules' ]
npm info linkStuff [email protected]
npm verb linkBins [email protected]
npm verb linkMans [email protected]
npm verb rebuildBundles [email protected]
npm info install [email protected]
npm verb unsafe-perm in lifecycle true

[email protected] install C:\test\node_modules\websocket
node install.js

from websocket-node.

Well it still ought to work without the native modules now after my changes.

from websocket-node.

Did this work? It says "npm info ok" at the end, but there's an error a little ways up. Hmm.

nils@THUNKI1 /c/test
$ npm install websocket --verbose
npm info it worked if it ends with ok
npm verb cli [ 'c:\Program Files\nodejs\node.exe',
npm verb cli 'c:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
npm verb cli 'install',
npm verb cli 'websocket',
npm verb cli '--verbose' ]
npm info using [email protected]
npm info using [email protected]
npm verb config file C:\Users\nils.npmrc
npm verb config file c:\Program Files\nodejs\etc\npmrc
npm verb config file c:\Program Files\nodejs\node_modules\npm\npmrc
npm verb read json c:\test\package.json
npm verb read json c:\test\package.json
npm verb cache add [ 'websocket', null ]
npm verb parsed url { pathname: 'websocket', path: 'websocket', href: 'websocket' }
npm verb lock websocket C:\Users\nils\AppData\Roaming\npm-cache\67c371fd-websocket.lock
npm verb addNamed [ 'websocket', '' ]
npm verb addNamed [ null, '' ]
npm verb lock websocket@ C:\Users\nils\AppData\Roaming\npm-cache\75462c75-websocket.lock
npm verb url raw websocket
npm verb url resolving [ 'https://registry.npmjs.org/', './websocket' ]
npm verb url resolved https://registry.npmjs.org/websocket
npm info retry registry request attempt 1 at 21:02:58
npm verb etag "1QDMMSUFG1Z4YMP2EWTRR27N0"
npm http GET https://registry.npmjs.org/websocket
npm http 304 https://registry.npmjs.org/websocket
npm verb etag websocket from cache
npm verb addNamed [ 'websocket', '1.0.7' ]
npm verb addNamed [ '1.0.7', '1.0.7' ]
npm verb lock [email protected] C:\Users\nils\AppData\Roaming\npm-cache\d81c032f-websocket-1-0-7.lock
npm verb read json C:\Users\nils\AppData\Roaming\npm-cache\websocket\1.0.7\package\package.json
npm info install [email protected] into c:\test
npm info installOne [email protected]
npm verb from cache C:\Users\nils\AppData\Roaming\npm-cache\websocket\1.0.7\package\package.json
npm info c:\test\node_modules\websocket unbuild
npm verb read json c:\test\node_modules\websocket\package.json
npm verb tar unpack C:\Users\nils\AppData\Roaming\npm-cache\websocket\1.0.7\package.tgz
npm verb lock c:\test\node_modules\websocket C:\Users\nils\AppData\Roaming\npm-cache\25bc9fad-c-test
-node-modules-websocket.lock
npm verb read json c:\test\node_modules\websocket\package.json
npm info preinstall [email protected]
npm verb from cache c:\test\node_modules\websocket\package.json
npm verb readDependencies using package.json deps
npm verb from cache c:\test\node_modules\websocket\package.json
npm verb readDependencies using package.json deps
npm verb about to build c:\test\node_modules\websocket
npm info build c:\test\node_modules\websocket
npm verb from cache c:\test\node_modules\websocket\package.json
npm verb linkStuff [ false, false, false, 'c:\test\node_modules' ]
npm info linkStuff [email protected]
npm verb linkBins [email protected]
npm verb linkMans [email protected]
npm verb rebuildBundles [email protected]
npm info install [email protected]
npm verb unsafe-perm in lifecycle true

[email protected] install c:\test\node_modules\websocket
node install.js

[websocket v1.0.7] Attempting to compile native extensions.
[websocket v1.0.7]
Native code compile failed!!
On Windows, native extensions require Visual Studio and Python.
On Unix, native extensions require Python, make and a C++ compiler.
Start npm with --websocket:verbose to show compilation output (if any).
npm info postinstall [email protected]
[email protected] node_modules\websocket
npm verb exit [ 0, true ]
npm info ok

nils@THUNKI1 /c/test
$

from websocket-node.

Yes, it should still work, it'll just disable verification that incoming messages are valid UTF-8, and the XOR unmasking of incoming frames will happen in JavaScript instead of native code.

from websocket-node.

You can run the npm install command with --websocket:verbose to see the actual compilation errors.

from websocket-node.

Awesome. Good to have that failsafe. :) Here's the output from the --websocket:verbose.

nils@THUNKI1 /c/test
$ npm install websocket --websocket:verbose
npm http GET https://registry.npmjs.org/websocket
npm http 304 https://registry.npmjs.org/websocket

[email protected] install c:\test\node_modules\websocket
node install.js

[websocket v1.0.7] Attempting to compile native extensions.

c:\test\node_modules\websocket>node "c:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin...
.\node_modules\node-gyp\bin\node-gyp.js" rebuild
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.Cpp.InvalidPlatform.Targets(23,7): error
MSB8007: The Platform for project 'validation.vcxproj' is invalid. Platform='x64'. You may be seei
ng this message because you are trying to build a project without a solution file, and have specifie
d a non-default Platform that doesn't exist for this project. [c:\test\node_modules\websocket\build
validation.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.Cpp.InvalidPlatform.Targets(23,7): error
MSB8007: The Platform for project 'xor.vcxproj' is invalid. Platform='x64'. You may be seeing this
message because you are trying to build a project without a solution file, and have specified a non
-default Platform that doesn't exist for this project. [c:\test\node_modules\websocket\build\xor.vcx
proj]
gyp[websocket v1.0.7]
Native code compile failed!!
On Windows, native extensions require Visual Studio and Python.
On Unix, native extensions require Python, make and a C++ compiler.
Start npm with --websocket:verbose to show compilation output (if any).
[email protected] node_modules\websocket

nils@THUNKI1 /c/test
$

from websocket-node.

Strange. Have you tried uninstalling and reinstalling visual studio? I don't think I have any special Win7 sdk installed on my end... maybe that has something to do with it? I'm not sure, I'm really not a Windows developer :-/

from websocket-node.

Phew! I must've tried installing/uninstalling Visual Studio 2010 and the Windows 7 sdk a couple of times. I am not sure if the Win7 sdk is required, but I managed to compile websockets just fine now (after having first installed the Win7 sdk and then Visual Studio C++ 2010). Thank you for your assistance! :)

from websocket-node.

Awesome! I'm glad you got it figured out! Presumably it was something with the Visual Studio installation then? I'll go ahead and close this issue for now.

Thanks!

from websocket-node.

I solved following this issue:
socketio/socket.io#1151

So I installed karma setting the version of VS to be used to compile socket.io, as shown below:
npm install karma -g -msvs_version=2012

from websocket-node.