5 ms·

Breach of trust or breach of security? Also why not going cross-platform?

by CmonDev 12y ago

alandarev 12y ago
I suspect the troubles of compiling npm dependencies on Windows - the same reason Atom was not readily available on Windows for a while.
- WorldWideWayne 12y ago
  It's actually no harder on Windows than it is on any other platform. On a Unix platform, you must install python, make and GCC. The readme for node-gyp states that the easiest way to get these for OS X is to install XCode. Windows users must install at the very least a free version of Visual Studio and Python 2.7. There's also node-pre-gyp to precompile binaries, which I would vastly prefer as a user and a developer. I suspect that ideology actually plays a larger part in these decisions than logistics. (EDIT: I could be wrong, but anyway they explain here that they need to move off of GTK+ before having a Windows build for some reason - https://github.com/breach/breach_core/issues/90 https://github.com/breach/breach_core/issues/90)
  - 0942v8653 12y ago
    I don't understand why people say that's the easiest way to do it. You can just run `cc` in a terminal and a dialog will pop up prompting you to install it.
  - tonetheman 12y ago
    Man do you have instructions on that Windows setup for node? I looked around for them the other day when something I was trying to installed failed miserably and found nothing. I might just be missing something obvious...
    - WorldWideWayne 12y ago
      To setup node on Windows you just download the installer and you're done. Nothing else is needed unless you want to compile native native binaries. To be able to compile native binaries, you need to just install Python 2.7 and Visual Studio. Depending on the version of Visual Studio that you have installed, you might have to pass an extra flag to npm when installing native packages that must be compiled. So, if you installed some version of Visual Studio 2012 or 2013 instead of the 2010 version, you might have to pass the "msvs_version" flag to npm like this: npm install socket.io --msvs_version=2012

Breach of trust or breach of security? Also why not going cross-platform?

by CmonDev 12y ago

Breach of trust or breach of security? Also why not going cross-platform?

I suspect the troubles of compiling npm dependencies on Windows - the same reason Atom was not readily available on Windows for a while.

WorldWideWayne 12y ago
It's actually no harder on Windows than it is on any other platform. On a Unix platform, you must install python, make and GCC. The readme for node-gyp states that the easiest way to get these for OS X is to install XCode. Windows users must install at the very least a free version of Visual Studio and Python 2.7. There's also node-pre-gyp to precompile binaries, which I would vastly prefer as a user and a developer. I suspect that ideology actually plays a larger part in these decisions than logistics. (EDIT: I could be wrong, but anyway they explain here that they need to move off of GTK+ before having a Windows build for some reason - https://github.com/breach/breach_core/issues/90 https://github.com/breach/breach_core/issues/90)
- 0942v8653 12y ago
  I don't understand why people say that's the easiest way to do it. You can just run `cc` in a terminal and a dialog will pop up prompting you to install it.
- tonetheman 12y ago
  Man do you have instructions on that Windows setup for node? I looked around for them the other day when something I was trying to installed failed miserably and found nothing. I might just be missing something obvious...
  - WorldWideWayne 12y ago
    To setup node on Windows you just download the installer and you're done. Nothing else is needed unless you want to compile native native binaries. To be able to compile native binaries, you need to just install Python 2.7 and Visual Studio. Depending on the version of Visual Studio that you have installed, you might have to pass an extra flag to npm when installing native packages that must be compiled. So, if you installed some version of Visual Studio 2012 or 2013 instead of the 2010 version, you might have to pass the "msvs_version" flag to npm like this: npm install socket.io --msvs_version=2012