On Friday, October 19, 2012 at 8:46 PM, Alex Kocharin wrote: > Hi Jerome, > > If you are going to use native node.js libraries, you'll almost certainly get > yourself a nice time figuring out how to compile it.
This is why the npm wall of shame (http://registry.npmjs.org/-/scripts?scripts=install,preinstall,postinstall&match=\bnode-waf\b (http://registry.npmjs.org/-/scripts?scripts=install,preinstall,postinstall&match=%5Cbnode-waf%5Cb)) exists -- as others have said, if you want to use dependencies that rely upon node-waf to build, you're in trouble, but if you have VS 12 Express installed and have something that builds its native dependencies node-gyp, chances are good that things will work out. > If you are going to use just javascript libraries, you have a chance that > everything will work out of the box, but I wouldn't count on it. I got a fairly substantial Node project to work on Windows with no code changes in under an hour yesterday. A couple of my integration test suites didn't work, but that's mostly because they relied upon external server binaries, working with paths on Windows is a huge pain, and my attempts to wrap my head around PowerShell were futile. > > Windows isn't POSIX-compatible, and that's one big pitfall. For example, just > imagine what would it take on windows to get processor or memory information. > It's just fs.readFile('/proc/cpuinfo') on unixes, but what about windows? > Yeah, that's about it. If you use the tools that Node provides you, though, you'll be in pretty OK shape. Most of the basic system information you might want is available either on the process global or via the core 'os' module. For instance, os.freemem, os.totalmem and os.cpus will give you processor and memory information. > > But it's certainly possible to run linux in a virtual box or remote computer > and share disk between them, so you can run an editor on windows pc, but > compile and test your app in linux. It's really not that tough to do everything on Windows. The biggest hassle is getting everything set up in the first place, and dealing with modules that depend on node-waf. F -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
