-
Notifications
You must be signed in to change notification settings - Fork 66
Build fails on Windows because of node-waf #3
Comments
Hmm. I haven't tested it on Windows, but I see no reason why it //jb (Sent from my phone - please excuse brevity and typos.) On 9 maj 2012, at 16:54, Olivier Louvignes
|
Yes, but it does require the package "dtrace-provider" that requires compilation via "node-waf". |
Dtrace-provider will likely not build on Windows, but it's just a On 10 maj 2012, at 19:32, Olivier Louvignes
|
To clarify; Using snmp-native as a dependency on Windows should work just fine. If it doesn't open an issue on whatever happens. Manually installing snmp-native on Windows might fail because npm will try to install the devDependencies, which require dtrace-provider. To get around that, edit node_modules/snmp-native/package.json to remove the snmpjs devDependency, rerun npm install in node_modules/snmp-native. |
I pushed a version 1.0.5 that doesn't include the dev dependencies in the shrinkwrap; possibly that is what you were hitting. Also, if installing locally, a "npm install --no-dev" will avoid pulling in the dev dependencies, avoiding the dtrace issue. |
Does this package is intended to run on Windows?
Looks like node team has decided to switch from waf to gyp for building native modules (cf. http://botsikas.blogspot.fr/2011/12/nodejs-modules-cross-platform.html).
Any chance you would update this very promising plugin so that it can be built on windows?
Edit: Looks like you are indeed using gyp & it's just a dependency that fails to build (dtrace-provider). So this issue is probably irrelevant.
Edit2: Maybe you could do some npm tweaking to consider dtrace as optional (check : restify/node-restify#100 (comment))
Regards!
The text was updated successfully, but these errors were encountered: