On Friday, July 11, 2014 6:39:38 AM UTC+10, Ryan Dahl wrote: > > > Problems that will be had: > 5. gyp will be a major legacy project to depend on if Chrome moves to gn. > 6. node will have to back port V8's build process to gyp if Chrome moves > to gn. >
Your last point seems unavoidable should gyp be decided to stay. Above problems were basically the main reason I created this thread in the first place. The positive side-effect of switching gyp to gn is great but shouldn't really be a reason to explore switching. Will ninja be added as a third party dependency (it's pretty simple to both build and install) or should a npm ecosystem also consider integrating the build tool as well? I wonder if there's been any thoughts on this matter in the npm camp. It'd be valuable feedback since they're probably involved in this as much as node itself. -- 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/db50b408-0b54-4bf1-8aa5-e0d94ada36ba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
