Installing for node-webkit v0.8.6

[ghost]

Hello!

It seems there is a problem with the compilation process for node-webkit v0.8.6. I'm using this command:

npm install sqlite3 --build-from-source --runtime=node-webkit --target_arch=ia32 --target=0.8.6

But it seems this version is not supported, because this error is displayed

stack Error: node-webkit version '0.8.6' not supported

But if I choose v0.8.5 instead of v0.8.6, there is no problem, even when using node-webkit 0.8.6, and I can use the module.

Is there any solution to this problem?

Regards

[Mithgol]

@remy-phelipot

Currently the latest sqlite3 npm package is version 2.2.3 authored on 15 Apr 2014 (GMT).

The fix for node-webkit v0.8.6 was introduced later in node-pre-gyp v0.5.18. It will be included in the next version of the sqlite3 package.

[Mithgol]

@springmeyer Would you npm publish the master branch as version 2.2.4? (This would immediately provide a fix for this issue, I hope.)

[aguilaredu]

@remy-phelipot instead of installing it as an npm package install it from the project master branch. npm install https://github.com/mapbox/node-sqlite3/tarball/master --build-from-source --runtime=node-webkit --target_arch=ia32 --target=0.8.6 That made it work for me, it still doesn't work with node webkit >0.9.0 or 0.10.0-rc1.

[Mithgol]

@eduardoag For node-webkit 0.10.0-rc1 you could try installing from the experimental travis-refactor branch instead of master; in other words, npm install https://github.com/mapbox/node-sqlite3/tarball/travis-refactor --build-from-source --runtime=node-webkit --target_arch=ia32 --target=0.10.0-rc1

(And, if you try, tell us if it's successful.)

[aguilaredu]

@Mithgol Well you just made my day. Tested and it is up and running with node-webkit 0.10.0-rc1

[ghost]

@eduardoag Ok, I will try that on Monday ;) Thanks!
@Mithgol When this fix will be published, It will be perfect ;)

[springmeyer]

master now works after #313, and soon I'll tag v2.2.4 which will fix this.

[ghost]

Thanks!

[Mithgol]

@remy-phelipot This issue should already be fixed by now. Please check.

[ghost]

@Mithgol The issue is fixed for me. Thanks