aboutsummaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-devtools/nodejs
AgeCommit message (Collapse)Author
2020-01-23nodejs: Fix build on big-endian targetsKhem Raj
Fixes ../deps/v8/src/runtime/runtime-utils.h:129:11: error: base operand of '->' has non-pointer type 'v8::internal::Object' 129 | return y->ptr() | (static_cast<ObjectPair>(x->ptr()) << 32); | ^~ Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Martin Jansa <Martin.Jansa@gmail.com> Cc: Guillaume Burel <guillaume.burel@stormshield.eu>
2020-01-23nodejs: upgrade to 12.14.1Martin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2020-01-23nodejs: use python3nativeMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2020-01-23nodejs: 10.17.0 -> 12.14.0Guillaume Burel
- 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 <guillaume.burel@stormshield.eu> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2020-01-22recipes: Replace using BBPATH with BBFILE_COLLECTIONS for meta-python2 checkKhem Raj
BBPATH check actually does not work Signed-off-by: Khem Raj <raj.khem@gmail.com>
2020-01-22recipes: Turn inherit classes from meta-py2 to conditional constructsKhem Raj
helps parsing without meta-py2 in mix Signed-off-by: Khem Raj <raj.khem@gmail.com>
2020-01-22nodejs: Build only when meta-py2 is includedKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2020-01-22meta-oe: Remove using python2Khem Raj
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 <raj.khem@gmail.com>
2019-12-01nodejs: Add PACKAGECONFIG share to allow other projects to use node as libraryAndreas Müller
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 <schnitzeltony@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-11-21nodejs: libatomic patch should be target specificKhem Raj
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 <raj.khem@gmail.com> Acked-by: Andreas Müller <schnitzeltony@gmail.com> Acked-by: Tim Orling <timothy.t.orling@linux.intel.com>
2019-11-13nodejs: support long directory names for ${B} / ${S}André Draszik
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 $@ && $(AR.$(TOOLSET)) crsT $@ $(filter %.o,$^) i.e. something like printf rm -f Release/obj.target/deps/v8/gypfiles/libv8_base.a && 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 <git@andred.net> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-11-13nodejs: use OE-provided compiler flags (arm)André Draszik
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 <git@andred.net> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-11-13nodejs: allow use of system gypAndré Draszik
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 <git@andred.net> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-11-13nodejs: delete all bundled deps in do_unpack() if neededAndré Draszik
We can delete bundled deps where system-provided counterparts should be used instead. Amongst others, this ensures they are not used accidentally. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-11-13nodejs: ensure to use correct compiler & flags alwaysAndré Draszik
NodeJS comes with an embedded, patched, version of gyp. Normally, gyp supports compiling for the build machine, e.g. native tools that need to be compiled to run during the build, and for the host, using different variables, e.g. CC and CC.host, etc. Most of this has been patched out in the NodeJS version of gyp, and essentially it only supports compiling using one compiler - ${CC}. This modification excludes LDFLAGS for native tools, and those still evaluate LDFLAGS.host (only). While this modified behaviour is OK for the OE use-case of building native and target tools separately, it means that this recipe can not work as-is with standard gyp, and wrong LDFLAGS are being used for some of the tools compiled (torque) in either case. By setting the make variables that gyp-generated makefiles inspect, we support use of unpatched gyp, and we ensure that all tools are compiled with correct LDFLAGS in either case. This now also allows us to drop the patch that had been applied to work-around this problem. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-11-07nodejs: allow use of system nghttp2André Draszik
We can't enable this by default, though, as nghttp2 is in the meta-networking layer, which might not be enabled. At least this gives people a simple way to do so if they want. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-11-01nodejs: allow use of system libuv (and make default)André Draszik
Use system libuv via PACKAGECONFIG by default. So far, nodejs had been built using its embedded copy of libuv, which we generally try to avoid, for the known reasons (independent updates, cve & license checks, etc). Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-11-01nodejs: Upgrade 10.16.3 -> 10.17.0Adrian Bunk
Patch applied upstream removed. Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-11-01nodejs: allow use of system c-ares (and make default)André Draszik
Use system c-ares via PACKAGECONFIG by default. So far, nodejs had been built using its embedded copy of c-ares, which we generally try to avoid, for the known reasons (independent updates, cve & license checks, etc). Notes: * otherwise nodejs uses its bundled version of c-ares * the PACKAGECONFIG variable is 'ares' so as to be in line with other uses of this (wget & curl recipes in OE core) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-09-07nodejs: Mark incompatible with risc-vKhem Raj
Arch is not yet supported Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-09-03nodejs: 10.16.2 -> 10.16.3Andrej Valek
- update nodejs to active 10.x LTS release 10.16.3 - include fix multiple HTTP/2 vulnerabilities Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-08-17nodejs: fix QA error about /usr/bin/python dependencyMartin Jansa
* fixes: ERROR: QA Issue: /usr/lib/node_modules/npm/node_modules/node-gyp/gyp/samples/samples contained in package nodejs-npm requires /usr/bin/python, but no providers found in RDEPENDS_nodejs-npm? [file-rdeps] Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-08-11nodejs: 10.16.0 -> 10.16.2Andrej Valek
- update nodejs to active 10.x LTS release 10.16.2. - add python running dependency due to samples.py requirements Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-07-10nodejs: 10.15.3 -> 10.16.0Andrej Valek
Update nodejs to active 10.x LTS release 10.16.0. - make dependencies configurable License checksum changed due to added bundled dependencies to: - siphash - large_pages - brotli Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-03-26nodejs: Update GCC 4.8 compat patchBrad Bishop
GCC 4.8 compatibility was lost moving from 10.15.1 to 10.15.3. Add another wrapper for std::make_unique to restore it. Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-03-22nodejs: upgrade 10.15.1 -> 10.15.3Andreas Müller
* 10.15.2 was a security release for CVE-2019-5737 [1] * 10.15.3 was a bugfix release [2] [1] https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.15.2 [2] https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.15.3 Signed-off-by: Andreas Müller <schnitzeltony@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-03-19nodejs: fix target ldflags usingAndrej Valek
- do not drop target LDFLAGS - even if the target LDFLAGS have been specified, tools like torque was linked with system libraries Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-02-22nodejs: fix additional compatibility with older gccAndrej Valek
- replace all occurrences of std::make_unique with wrapper - sync indent level Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-02-17nodejs 8.15.0 -> 10.15.1Andrej Valek
Update nodejs to active 10.x LTS release 10.15.1. - link atomic library - make it compatible with gcc < 4.9 Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-01-28nodejs 8.14.0 -> 8.15.0Matthijs Vader
Update nodejs to latest 8.x stable release 8.15.0. Signed-off-by: Matthijs Vader <mvader@victronenergy.com> Signed-off-by: Jeroen Hofstee <jhofstee@victronenergy.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-12-04nodejs: 8.12.0 -> 8.14.0Andrej Valek
Update nodejs to latest 8.x stable release 8.14.0. Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-10-12nodejs: Enable system ICU supportKhem Raj
Latest Chromium needs it during build Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-10-08nodejs: Revert unintended changes (not ready yet)Khem Raj
We need to enable icu with intl support but this was accidentally committed with last umip move patch Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-10-07umip: fix recipe location typoHongxu Jia
Since `36983fe umip: move to meta-networking' applied, it was moved to invalid location. Fix prior partial move to meta-networking Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-09-25nodejs: upgrade to 8.12.0Hong Liu
Upgrade nodejs from 8.11.4 to 8.12.0. Signed-off-by: Hong Liu <hongl.fnst@cn.fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-08-28nodejs: 8.11.3 -> 8.11.4Hong Liu
Upgrade nodejs from 8.11.3 to 8.11.4 Signed-off-by: Hong Liu <hongl.fnst@cn.fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-07-03nodejs: update to 8.11.3Pascal Bach
Fixes the following CVEs: - CVE-2018-7167 - CVE-2018-7161 - CVE-2018-1000168 Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-06-08nodejs: 8.9.4 -> 8.11.2Pascal Bach
Node.js > 8.10 also compile with OpenSSL 1.1 License check sum changes because typo fix in LICENSE file. No license change. Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-03-12nodejs: add extra RDEPENDS for buildingTrevor Woerner
If you want to perform an "npm install" and a module needs to be compiled, these additional packages need to be on the target otherwise the compile might fail with one or more of the following error messages: ImportError: No module named compiler.ast ImportError: No module named filecmp ImportError: No module named multiprocessing Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Armin Kuster <akuster808@gmail.com>
2018-03-01nodejs: Update from 8.9.0 -> 8.9.4Parthiban Nallathambi
Update nodejs to latest stable release 8.9.4 Signed-off-by: Parthiban Nallathambi <pn@denx.de> Signed-off-by: Armin Kuster <akuster808@gmail.com>
2018-03-01nodejs: Add support for building on ppc64leGunnar Mills
ppc64le is a little-endian mode of ppc64. Nodejs determines the endianness of the system and since it already supports bi-endian ppc64, just pass nodejs "ppc64" when the TARGET_ARCH is ppc64le. Signed-off-by: Gunnar Mills <gmills@linux.vnet.ibm.com> Signed-off-by: Armin Kuster <akuster808@gmail.com>
2017-11-15nodejs: Update to 8.9.0Davis, Michael
Update nodejs to latest stable release 8.9.0. Signed-off-by: Armin Kuster <akuster808@gmail.com>
2017-10-27nodejs: Update to 8.7.0Jonathan Liu
LICENSE checksum updated due to copyright and formatting changes. Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-10-27nodejs: Remove unreferenced patchesJonathan Liu
Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-10-17nodejs: Add npx to nodejs-npm packageJonathan Liu
${bindir}/npx is a symbolic link to npm-cli.js in the npm module. This avoids the nodejs package depending on nodejs-npm. Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-08-31nodejs: Upgrade to 8.4.0Khem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-06-05nodejs: update to 4.8.3fan.xin
Signed-off-by: Fan Xin <fan.xin@jp.fujitsu.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-04-26nodejs: update to 4.8.2Pascal Bach
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-02-22nodejs: update to version 4.7.3Derek Straka
Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-01-25nodejs: update to 4.7.2Oleksandr Kravchuk
Signed-off-by: Oleksandr Kravchuk <oleksandr.kravchuk@pelagicore.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-05-27 04:23:10 +0000