make fails on Windows when PATH doesn't include '.'

[websockets]

make fails on Windows when PATH doesn't include '.'

[einaros]

This isn't necessarily easy to circumvent. Are you running this through some custom installer?

[martinthomson]

Just running npm.cmd install socket.io. It's part of a build process that has a controlled environment. Adding '.' to the path is possible, but not desirable. Maybe you could create a preinstall.js script that did the necessary magic (I don't fully understand why you need a Makefile) and run 'node preinstall' instead of make.

[einaros]

To start with the end: I need a makefile on non-windows systems to build the native extensions. The native extensions, in turn, makes ws much faster than it'd be with plain JavaScript, in addition to providing actual utf8 verification of the incoming stream.

Regarding a preinstall script, this is possible as well, but it would require some finesse. In specialized build environments such as the one you are using I can't even guarantee that node is in the path, so executing a preinstall.js could fail for completely different reasons.

This will all change in future versions of node (0.7+), when the gyp build system replaces node-waf. Any sort-of-working hack would thus just be temporary, and probably not be a catch-all in either case. I think I'll just have to say that any specialized build system will have to be adapted (such as adding . to the path, or actually running npm install from within the actual project directory).

In either case, I'll get back to you on this in the morning. I may decide to work around it.

[martinthomson]

Integrating different build systems is a complicated process. Obviously, since you have special requirements, you end up with special problems. Whatever you judge to be the best.