Am 09.07.2014 um 20:40 schrieb mscdex <[email protected]>: > On Wednesday, July 9, 2014 2:06:53 PM UTC-4, Ingwie Phoenix wrote: > I actually always wondered: We have a scripting engine. Why do we rely on > Python for GYP, if we have NodeJS? Is there no gyp replacement in node itself? > > > I would think the problem would be when you're building from source and and > do not already have node installed. Otherwise a node executable would have to > be downloaded/embedded to run the build script, at which point you may as > well just use/install the downloaded/embedded node binary ;-) > > I think Python is commonly already installed enough that it's rarely a > problem. I was rather pointing towards node-gyp here, to be honest.
Node-gyp relys on Python, due to GYP. And in fact, not everyone has Python installed. Windows for one, and not all linux distributions for the other. Mac does, but I have seen python devs ranting about the delivered vesion (to be fair, OS X had PHP 5.3 still, while 5.5 was marked stable/current. :P) I wonder if in the future, node's default extension building will be handled thru nodejs itself. But - when building nodejs from source - I totally would go for GN. Its lightweight and fast. And from what I remember, not bound to python...just some C++ compiler. Again, I have not come across any full GN source tree. -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/49C6C89C-4C5D-43A0-AE00-FFF155516DD5%40googlemail.com. For more options, visit https://groups.google.com/d/optout.
