<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-openembedded.git/meta-oe/recipes-devtools/nodejs/nodejs_10.17.0.bb, branch nanbield</title>
<subtitle>Mirror of git.openembedded.org/meta-openembedded</subtitle>
<id>https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=nanbield</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=nanbield'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/'/>
<updated>2020-01-23T22:16:25+00:00</updated>
<entry>
<title>nodejs: 10.17.0 -&gt; 12.14.0</title>
<updated>2020-01-23T22:16:25+00:00</updated>
<author>
<name>Guillaume Burel</name>
<email>guillaume.burel@stormshield.eu</email>
</author>
<published>2020-01-20T17:04:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=feeb172d1a8bf010490d22b8df9448b20d9d2aed'/>
<id>urn:sha1:feeb172d1a8bf010490d22b8df9448b20d9d2aed</id>
<content type='text'>
- update Node.js to active 12.x LTS release 12.14.0.
- remove compatibility with gcc 4.8 (has been removed upstream)

Signed-off-by: Guillaume Burel &lt;guillaume.burel@stormshield.eu&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>recipes: Replace using BBPATH with BBFILE_COLLECTIONS for meta-python2 check</title>
<updated>2020-01-23T03:21:39+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2020-01-23T03:08:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=e4a2593a2193922ef23e62d43affe15b50d825d7'/>
<id>urn:sha1:e4a2593a2193922ef23e62d43affe15b50d825d7</id>
<content type='text'>
BBPATH check actually does not work

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>recipes: Turn inherit classes from meta-py2 to conditional constructs</title>
<updated>2020-01-22T22:20:35+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2020-01-22T22:17:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=8c0c7f0a37a1b4a7eb7ea585971534cd1e481b8e'/>
<id>urn:sha1:8c0c7f0a37a1b4a7eb7ea585971534cd1e481b8e</id>
<content type='text'>
helps parsing without meta-py2 in mix

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>nodejs: Build only when meta-py2 is included</title>
<updated>2020-01-22T17:56:35+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2020-01-22T06:28:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=0a4faceed66002ca04413f69f6b422197981cedf'/>
<id>urn:sha1:0a4faceed66002ca04413f69f6b422197981cedf</id>
<content type='text'>
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>meta-oe: Remove using python2</title>
<updated>2020-01-22T17:56:34+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2020-01-20T00:33:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=505774658338002a92c2e32c4c57c55f36c5e36e'/>
<id>urn:sha1:505774658338002a92c2e32c4c57c55f36c5e36e</id>
<content type='text'>
This change makes the parsing go though, we still might have build
issues, which will be reported in world builds seprately

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>nodejs: Add PACKAGECONFIG share to allow other projects to use node as library</title>
<updated>2019-12-02T06:29:59+00:00</updated>
<author>
<name>Andreas Müller</name>
<email>schnitzeltony@gmail.com</email>
</author>
<published>2019-12-01T16:51:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=f0f6c0174dd6e9b526f5a6bf1955a3aed9250ef5'/>
<id>urn:sha1:f0f6c0174dd6e9b526f5a6bf1955a3aed9250ef5</id>
<content type='text'>
There are so many useful modules written for node.js I would like to use in
C++/Qt projects.

Run-tested both variants by installing node-red with npm and running it.

Signed-off-by: Andreas Müller &lt;schnitzeltony@gmail.com&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>nodejs: libatomic patch should be target specific</title>
<updated>2019-11-22T01:52:26+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2019-11-21T18:24:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=86d4131dfabdf4bca27d96de6f271565f1a3a5c6'/>
<id>urn:sha1:86d4131dfabdf4bca27d96de6f271565f1a3a5c6</id>
<content type='text'>
host usually are using gcc/x86_64/aarch64 and all of them have gcc which
can support atomic intrinsics, but not all of them install libatomic by
default e.g. centos-7, so asking for libatomic unconditionally may not
work always

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Acked-by: Andreas Müller &lt;schnitzeltony@gmail.com&gt;
Acked-by: Tim Orling &lt;timothy.t.orling@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>nodejs: support long directory names for ${B} / ${S}</title>
<updated>2019-11-13T15:17:03+00:00</updated>
<author>
<name>André Draszik</name>
<email>git@andred.net</email>
</author>
<published>2019-11-10T22:05:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=57345467282da25593db2b340a1dc5551354bc88'/>
<id>urn:sha1:57345467282da25593db2b340a1dc5551354bc88</id>
<content type='text'>
Part of the NodeJS build builds V8, which at some stage tries to call
ar with all objects with *absolute* paths (and printf the command line
first).

This will fail if the build path is too long:
    make[1]: execvp: printf: Argument list too long
when trying to create Release/obj.target/deps/v8/gypfiles/libv8_base.a
via below gyp-generated out/Makefile rule:
    cmd_alink_thin = rm -f $@ &amp;&amp; $(AR.$(TOOLSET)) crsT $@ $(filter %.o,$^)
i.e. something like
    printf rm -f Release/obj.target/deps/v8/gypfiles/libv8_base.a &amp;&amp; arm-poky-linux-musleabi-gcc-ar crsT Release/obj.target/deps/v8/gypfiles/libv8_base.a ...

The above failure happened on a build-directory S with 204 characters
on a Jenkins machine.

While one could probably increase the ulimit on that specific machine,
that would be a pretty specific build machine fix which would need to
be applied everywhere, or switch to non-verbose builds / compilation,
but fortunately we can change all object references to be relative to
the build directory itself by setting the builddir_name make variable
and thus avoid the other two possible work-arounds.

Signed-off-by: André Draszik &lt;git@andred.net&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>nodejs: use OE-provided compiler flags (arm)</title>
<updated>2019-11-13T15:17:03+00:00</updated>
<author>
<name>André Draszik</name>
<email>git@andred.net</email>
</author>
<published>2019-11-10T22:05:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=c174217540abebac63498cf2f8ae429662c15fec'/>
<id>urn:sha1:c174217540abebac63498cf2f8ae429662c15fec</id>
<content type='text'>
This overrides yocto-provided build flags with its own, e.g we get
    arm-poky-linux-musleabi-g++  -mthumb -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a7 \
                                 ... \
                                  -march=armv7-a -mfpu=neon -mfloat-abi=hard -marm

Causing the latter to override the former, and compiler warnings:
    cc1plus: warning: switch '-mcpu=cortex-a7' conflicts with '-march=armv7-a' switch

Patch this out, so that yocto-provided flags take precedence.
Note that in reality the same should probably be done for all the other
supported architectures, too.

Note that this also switches to Thumb(2) mode (in my case). No obvious
problems have been noted during compilation or runtime.

Upstream-Status: Inappropriate [oe-specific]
Signed-off-by: André Draszik &lt;git@andred.net&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>nodejs: allow use of system gyp</title>
<updated>2019-11-13T15:17:03+00:00</updated>
<author>
<name>André Draszik</name>
<email>git@andred.net</email>
</author>
<published>2019-11-10T22:05:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=0d4a59268cc696171534f6ddfbedc91a2b3abf1a'/>
<id>urn:sha1:0d4a59268cc696171534f6ddfbedc91a2b3abf1a</id>
<content type='text'>
Now that there is a gyp (python2) recipe in meta-python,
allow its use instead of the bundled one for when
meta-python is enabled.

At the same time, unconditionally inherit pythonnative
as in either case gyp actually uses python, and the
build machine's python and installed modules should
never be used.

Signed-off-by: André Draszik &lt;git@andred.net&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
</feed>
