From: "António Oliveira" <antonio.oliveira@konsulko.com>
To: yocto@lists.yoctoproject.org
Cc: "António Oliveira" <antonio.oliveira@konsulko.com>
Subject: [RFC PATCH v2 0/3] lts mixin: kirkstone/nodejs proposal
Date: Mon, 8 Jan 2024 15:58:35 +0000 [thread overview]
Message-ID: <cover.1704728801.git.antonio.oliveira@konsulko.com> (raw)
In-Reply-To: <20231204183055.29931-1-antonio@amsobr.com>
Hi all,
This patch contains my proposal for an mixin layer that adds nodejs v18
to kirkstone.
Kirkstone ships with nodejs-16, whose maintenance window ended in
October 2023 (a).
Kirkstone will be supported until April 2026 and it would be nice to have
some level of support for a maintained version of nodejs during that time
window.
This proposal seeks to address that by adding nodejs-18, which will be
maintained until April 2025.
The recipes for nodejs-18 are taken from Mickledore
The variable NODE_VERSION is set from the layer configuration to select
nodejs-18. It can be overridden in case anyone wants to use any other.
This is my first attempt at sending a patch upstream with git send-email
so any comments or suggestions for improvement are welcome. That's also
the reason why I marked this as an RFC.
Revisions of this proposal:
v1:
* Initial attempt at this proposal with nodejs-18 and nodejs-20
v2
* split into smaller commits
* included José's suggestion of adding the dependency on the
"openembedded-layer" due to default configuration settings of nodejs.
* Updating to the latest nodejs-20 recipes forced me to also backport
icu_74-1 from master. Sadly this broke a build of lvgl and I opted to
keep nodejs-20 on the backburner for now.
Cheers,
António
António Oliveira (3):
initial commit: license, readme, conf
add nodejs-18 from mickledore
add layer configuration for default node
COPYING.MIT | 17 ++
README | 22 +++
conf/layer.conf | 21 ++
.../nodejs/nodejs-oe-cache-18.18/oe-npm-cache | 77 ++++++++
.../nodejs/nodejs-oe-cache-native_18.18.bb | 21 ++
...e-running-gyp-files-for-bundled-deps.patch | 51 +++++
.../nodejs/0001-Using-native-binaries.patch | 77 ++++++++
...-liftoff-Correct-function-signatures.patch | 85 ++++++++
...Use-32bit-cast-for-operand-on-mips32.patch | 34 ++++
...4-Do-not-use-mminimal-toc-with-clang.patch | 23 +++
.../0004-v8-don-t-override-ARM-CFLAGS.patch | 102 ++++++++++
.../nodejs/nodejs/big-endian.patch | 18 ++
.../nodejs/nodejs/libatomic.patch | 21 ++
.../nodejs/nodejs/mips-less-memory.patch | 37 ++++
recipes-devtools/nodejs/nodejs/run-ptest | 3 +
.../nodejs/nodejs/system-c-ares.patch | 24 +++
recipes-devtools/nodejs/nodejs_18.18.2.bb | 185 ++++++++++++++++++
17 files changed, 818 insertions(+)
create mode 100644 COPYING.MIT
create mode 100644 README
create mode 100644 conf/layer.conf
create mode 100755 recipes-devtools/nodejs/nodejs-oe-cache-18.18/oe-npm-cache
create mode 100644 recipes-devtools/nodejs/nodejs-oe-cache-native_18.18.bb
create mode 100644 recipes-devtools/nodejs/nodejs/0001-Disable-running-gyp-files-for-bundled-deps.patch
create mode 100644 recipes-devtools/nodejs/nodejs/0001-Using-native-binaries.patch
create mode 100644 recipes-devtools/nodejs/nodejs/0001-liftoff-Correct-function-signatures.patch
create mode 100644 recipes-devtools/nodejs/nodejs/0001-mips-Use-32bit-cast-for-operand-on-mips32.patch
create mode 100644 recipes-devtools/nodejs/nodejs/0001-ppc64-Do-not-use-mminimal-toc-with-clang.patch
create mode 100644 recipes-devtools/nodejs/nodejs/0004-v8-don-t-override-ARM-CFLAGS.patch
create mode 100644 recipes-devtools/nodejs/nodejs/big-endian.patch
create mode 100644 recipes-devtools/nodejs/nodejs/libatomic.patch
create mode 100644 recipes-devtools/nodejs/nodejs/mips-less-memory.patch
create mode 100755 recipes-devtools/nodejs/nodejs/run-ptest
create mode 100644 recipes-devtools/nodejs/nodejs/system-c-ares.patch
create mode 100644 recipes-devtools/nodejs/nodejs_18.18.2.bb
--
2.34.1
next prev parent reply other threads:[~2024-01-08 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 18:30 [RFC PATCH 0/1] lts mixin: kirkstone/nodejs proposal António Oliveira
2023-12-04 18:30 ` [RFC PATCH 1/1] initial commit António Oliveira
2023-12-05 10:32 ` [yocto] " Jose Quaresma
2023-12-05 18:21 ` António Oliveira
2023-12-05 10:44 ` [yocto] [RFC PATCH 0/1] lts mixin: kirkstone/nodejs proposal Jose Quaresma
2023-12-05 18:26 ` António Oliveira
2023-12-07 11:07 ` Jose Quaresma
2024-01-08 15:58 ` António Oliveira [this message]
2024-01-08 15:58 ` [RFC PATCH v2 1/3] initial commit: license, readme, conf António Oliveira
2024-01-08 15:58 ` [RFC PATCH v2 2/3] add nodejs-18 from mickledore António Oliveira
2024-01-08 15:58 ` [RFC PATCH v2 3/3] add layer configuration for default node António Oliveira
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=cover.1704728801.git.antonio.oliveira@konsulko.com \
--to=antonio.oliveira@konsulko.com \
--cc=yocto@lists.yoctoproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox