From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] swig: enable support for Node.js >= 7.x
Date: Sun, 8 Oct 2017 20:50:31 +0200 [thread overview]
Message-ID: <20171008205031.44850462@windsurf> (raw)
In-Reply-To: <CAGm1_kvanZjOBLtt4N+ucMhKJ1u+Y6vowr4Gju6rp5dM_LYjCg@mail.gmail.com>
Hello,
On Sun, 8 Oct 2017 19:16:11 +0200, Yegor Yefremov wrote:
> > To be honest, I hesitated a bit, those patches are a bit big and
> > invasive, and have not been merged upstream yet. I've merged anyway,
> > but we might need to drop them at the next swig bump if they haven't
> > been merged upstream.
>
> Thanks for merging. The problem is that the project lacks a Node.js
> maintainer. That's why none has applied the patch.
Hopefully with all the comments received in the github PR, the Node.js
maintainers will apply those patches.
> SWIG as such has nothing to do with Node.js directly, but it creates
> code, that will be compiled against node.js via node-gyp utility [1].
> BR uses newest Node.js version with removed obsolete APIs. That's why
> we need this patch, but SWIG has no direct dependency to host-nodejs.
OK, makes sense. Thanks for the explanation!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-10-08 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 11:59 [Buildroot] [PATCH] swig: enable support for Node.js >= 7.x yegorslists at googlemail.com
2017-10-08 13:52 ` Thomas Petazzoni
2017-10-08 17:16 ` Yegor Yefremov
2017-10-08 18:50 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171008205031.44850462@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.