Re: Avoiding the hard build dependency on NodeJS

On Wed, Nov 7, 2018 at 5:35 AM Martin Husemann wrote: > I understand the desire for developers do use the best tool for each job, > and integrating NodeJS in the regular work flow during development might be > a good idea. > > However, requiring NodeJS for each build (including the official relea

Re: Avoiding the hard build dependency on NodeJS

On 11/7/18 9:30 AM, Martin Husemann wrote: Or port node to Spidermonkey, might be easier :-) True. https://github.com/mozilla/spidernode/ is not really active, but might be revivable... -Boris ___ dev-builds mailing list dev-builds@lists.mozilla.o

Re: Avoiding the hard build dependency on NodeJS

On Wednesday, November 7, 2018 at 3:23:02 PM UTC+1, Boris Zbarsky wrote: > You'd need to port V8 to work on sparc, right? That sounds fairly > painful... Or port node to Spidermonkey, might be easier :-) ___ dev-builds mailing list dev-builds@lists.mo

Re: Avoiding the hard build dependency on NodeJS

On 11/7/18 8:32 AM, Martin Husemann wrote: NodeJS seems to have no support at all for sparc CPUs, and I am not yet sure how hard it would be to add. You'd need to port V8 to work on sparc, right? That sounds fairly painful... -Boris ___ dev-build

Avoiding the hard build dependency on NodeJS

I understand the desire for developers do use the best tool for each job, and integrating NodeJS in the regular work flow during development might be a good idea. However, requiring NodeJS for each build (including the official releases) causes great problems: NodeJS itself is way less portable