Ilkka Myller

/cc @bachp @gizero @ofrobots

Documented Node v7 requirements to master branch README in commit https://github.com/imyller/meta-nodejs/commit/0b66df51c1023bb7d2506aee16394774d79ca38a Hopefully we can resolve the issue and remove this doc before merging v7 in `krogoth` branch.

No progress yet. Looks like we are going to have to kindly ask Yocto to include `g++-multilib` (in addition to existing `gcc-multilib`) to host/build system package requirements. I'm not too...

Node.js v7.x.x is now in `krogoth` branch. Unfortunately `g++-multilib` is now build system dependency for all Yocto versions when building Node.js v7 or newer.

I'll land this along with Node.js v8.0.0

Yes, Node.js upstream is dropping support for the now previous-`Current` line v7.x.x at the end of June 2017 and Node.js 8 will be new `Current` release - starting yesterday -...

I see no reason why you couldn't use grunt or any other automated method for minifying assets when building the package. You have `nodejs-native` running locally on build host during...

I agree with @gizero Looks like meta-nodejs is not included.

@joaopaulob If bundled openssl compilation fails you can build Node.js with use shared openssl. This can be enabled with `PACKAGECONFIG`: http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#var-PACKAGECONFIG For example, in your `local.conf` ``` PACKAGECONFIG_append_pn-nodejs = "...

I've been thinking the same thing myself. 👍 for this effort. I agree that using shared OpenSSL would be better for OE builds. However, I'd still keep zlib internal. It's...